MERCURY SYSTEMS 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
Mercury Systems Inc quarterly/annual Share-based Payment Arrangement, Expense history and growth rate from 2012 to 2023.
  • Mercury Systems Inc Share-based Payment Arrangement, Expense for the quarter ending June 28, 2024 was $7.25M.
  • Mercury Systems Inc Share-based Payment Arrangement, Expense for the twelve months ending June 28, 2024 was $25.7M.
  • Mercury Systems Inc annual Share-based Payment Arrangement, Expense for 2023 was $25.7M, a 33% decline from 2022.
  • Mercury Systems Inc annual Share-based Payment Arrangement, Expense for 2022 was $38.3M, a 35.4% increase from 2021.
  • Mercury Systems Inc annual Share-based Payment Arrangement, Expense for 2021 was $28.3M, a 6.6% 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 $25.7M -$12.6M -33% Jul 1, 2023 Jun 28, 2024 10-K 2024-08-13
2022 $38.3M +$10M +35.4% Jul 3, 2021 Jul 1, 2022 10-K 2024-08-13
2021 $28.3M +$1.75M +6.6% Jul 4, 2020 Jul 2, 2021 10-K 2023-08-15
2020 $26.5M +$7.12M +36.6% Jul 1, 2019 Jul 3, 2020 10-K 2022-08-16
2019 $19.4M +$2.11M +12.2% Jul 1, 2018 Jun 30, 2019 10-K 2021-08-17
2018 $17.3M +$1.97M +12.9% Jul 1, 2017 Jun 30, 2018 10-K 2020-08-18
2017 $15.3M +$5.77M +60.2% Jul 1, 2016 Jun 30, 2017 10-K 2019-08-15
2016 $9.57M +$934K +10.8% Jul 1, 2015 Jun 30, 2016 10-K 2018-08-16
2015 $8.64M -$359K -3.99% Jul 1, 2014 Jun 30, 2015 10-K 2017-08-18
2014 $9M +$1.15M +14.6% Jul 1, 2013 Jun 30, 2014 10-K 2016-08-16
2013 $7.85M +$1.28M +19.5% Jul 1, 2012 Jun 30, 2013 10-K 2015-08-13
2012 $6.57M Jul 1, 2011 Jun 30, 2012 10-K 2014-08-14
* An asterisk sign (*) next to the value indicates that the value is likely invalid.