SIRIUS XM HOLDINGS INC. Annual Share-based Payment Arrangement, Expense in USD from 2010 to 2024

Taxonomy & unit
us-gaap: USD
Description
Amount of expense for award under share-based payment arrangement. Excludes amount capitalized.
Summary
Sirius Xm Holdings Inc. quarterly/annual Share-based Payment Arrangement, Expense history and growth rate from 2010 to 2024.
  • Sirius Xm Holdings Inc. Share-based Payment Arrangement, Expense for the quarter ending December 31, 2024 was $51M, a 13.6% decline year-over-year.
  • Sirius Xm Holdings Inc. Share-based Payment Arrangement, Expense for the twelve months ending December 31, 2024 was $200M, a 1.48% decline year-over-year.
  • Sirius Xm Holdings Inc. annual Share-based Payment Arrangement, Expense for 2024 was $200M, a 1.48% decline from 2023.
  • Sirius Xm Holdings Inc. annual Share-based Payment Arrangement, Expense for 2023 was $203M, a 2.87% decline from 2022.
  • Sirius Xm Holdings Inc. annual Share-based Payment Arrangement, Expense for 2022 was $209M, a 3.47% increase from 2021.
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
2024 $200M -$3M -1.48% Jan 1, 2024 Dec 31, 2024 10-K 2025-01-30
2023 $203M -$6M -2.87% Jan 1, 2023 Dec 31, 2023 10-K 2025-01-30
2022 $209M +$7M +3.47% Jan 1, 2022 Dec 31, 2022 10-K 2025-01-30
2021 $202M -$21M -9.42% Jan 1, 2021 Dec 31, 2021 10-K 2024-02-01
2020 $223M -$27M -10.8% Jan 1, 2020 Dec 31, 2020 10-K 2023-02-02
2019 $250M +$117M +88% Jan 1, 2019 Dec 31, 2019 10-K 2022-02-01
2018 $133M +$9M +7.26% Jan 1, 2018 Dec 31, 2018 10-K 2021-02-02
2017 $124M Jan 1, 2017 Dec 31, 2017 10-K 2020-02-04
2012 $63.8M +$12.2M +23.6% Jan 1, 2012 Dec 31, 2012 10-K 2013-02-06
2011 $51.6M -$2.96M -5.43% Jan 1, 2011 Dec 31, 2011 10-K 2013-02-06
2010 $54.6M Jan 1, 2010 Dec 31, 2010 10-K 2013-02-06
* An asterisk sign (*) next to the value indicates that the value is likely invalid.