CareDx, Inc. Annual Share-based Payment Arrangement, Expense in USD from 2012 to 2023

Taxonomy & unit
us-gaap: USD
Description
Amount of expense for award under share-based payment arrangement. Excludes amount capitalized.
Summary
CareDx, Inc. quarterly/annual Share-based Payment Arrangement, Expense history and growth rate from 2012 to 2023.
  • CareDx, Inc. Share-based Payment Arrangement, Expense for the quarter ending June 30, 2024 was $13.2M, a 3.7% increase year-over-year.
  • CareDx, Inc. Share-based Payment Arrangement, Expense for the twelve months ending June 30, 2024 was $49.1M, a 1.27% decline year-over-year.
  • CareDx, Inc. annual Share-based Payment Arrangement, Expense for 2023 was $49.1M, a 5.44% increase from 2022.
  • CareDx, Inc. annual Share-based Payment Arrangement, Expense for 2022 was $46.6M, a 29% increase from 2021.
  • CareDx, Inc. annual Share-based Payment Arrangement, Expense for 2021 was $36.1M, a 54.2% 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 $49.1M +$2.53M +5.44% Jan 1, 2023 Dec 31, 2023 10-K 2024-02-28
2022 $46.6M +$10.5M +29% Jan 1, 2022 Dec 31, 2022 10-K 2024-02-28
2021 $36.1M +$12.7M +54.2% Jan 1, 2021 Dec 31, 2021 10-K 2024-02-28
2020 $23.4M +$984K +4.39% Jan 1, 2020 Dec 31, 2020 10-K 2023-02-27
2019 $22.4M +$15.3M +214% Jan 1, 2019 Dec 31, 2019 10-K 2022-02-24
2018 $7.14M +$5.39M +309% Jan 1, 2018 Dec 31, 2018 10-K 2021-02-24
2017 $1.74M -$254K -12.7% Jan 1, 2017 Dec 31, 2017 10-K 2020-02-28
2016 $2M +$657K +49% Jan 1, 2016 Dec 31, 2016 10-K 2019-03-06
2015 $1.34M +$806K +151% Jan 1, 2015 Dec 31, 2015 10-K 2018-03-22
2014 $535K +$463K +643% Jan 1, 2014 Dec 31, 2014 10-K 2017-04-21
2013 $72K +$3K +4.35% Jan 1, 2013 Dec 31, 2013 10-K 2016-03-29
2012 $69K Jan 1, 2012 Dec 31, 2012 10-K 2015-03-31
* An asterisk sign (*) next to the value indicates that the value is likely invalid.