iRhythm Technologies, Inc. Annual Share-based Payment Arrangement, Expense in USD from 2014 to 2023

Taxonomy & unit
us-gaap: USD
Description
Amount of expense for award under share-based payment arrangement. Excludes amount capitalized.
Summary
iRhythm Technologies, Inc. quarterly/annual Share-based Payment Arrangement, Expense history and growth rate from 2014 to 2023.
  • iRhythm Technologies, Inc. Share-based Payment Arrangement, Expense for the quarter ending September 30, 2024 was $17.2M, a 18.3% decline year-over-year.
  • iRhythm Technologies, Inc. Share-based Payment Arrangement, Expense for the twelve months ending September 30, 2024 was $83.8M, a 21.2% increase year-over-year.
  • iRhythm Technologies, Inc. annual Share-based Payment Arrangement, Expense for 2023 was $77.2M, a 33.7% increase from 2022.
  • iRhythm Technologies, Inc. annual Share-based Payment Arrangement, Expense for 2022 was $57.7M, a 5.89% increase from 2021.
  • iRhythm Technologies, Inc. annual Share-based Payment Arrangement, Expense for 2021 was $54.5M, a 31.3% increase from 2020.
Share-based Payment Arrangement, Expense, Trailing 12 Months (USD)
Share-based Payment Arrangement, Expense, Annual (USD)
Share-based Payment Arrangement, Expense, YoY Annual Growth (%)
Period Value YoY Chg Change % Start Date End Date Report Filed
2023 $77.2M +$19.5M +33.7% Jan 1, 2023 Dec 31, 2023 10-K 2024-02-22
2022 $57.7M +$3.21M +5.89% Jan 1, 2022 Dec 31, 2022 10-K 2024-02-22
2021 $54.5M +$13M +31.3% Jan 1, 2021 Dec 31, 2021 10-K 2024-02-22
2020 $41.5M +$15.3M +58.2% Jan 1, 2020 Dec 31, 2020 10-K 2023-02-23
2019 $26.2M +$9.91M +60.7% Jan 1, 2019 Dec 31, 2019 10-K 2022-02-28
2018 $16.3M +$6.58M +67.4% Jan 1, 2018 Dec 31, 2018 10-K 2021-02-26
2017 $9.75M +$7.88M +421% Jan 1, 2017 Dec 31, 2017 10-K 2020-03-02
2016 $1.87M +$461K +32.7% Jan 1, 2016 Dec 31, 2016 10-K 2019-03-04
2015 $1.41M +$582K +70.3% Jan 1, 2015 Dec 31, 2015 10-K 2018-03-01
2014 $828K Jan 1, 2014 Dec 31, 2014 10-K 2017-03-31
* An asterisk sign (*) next to the value indicates that the value is likely invalid.