L3HARRIS TECHNOLOGIES, INC. /DE/ 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
L3 Harris Technologies, Inc. /De/ quarterly/annual Share-based Payment Arrangement, Expense history and growth rate from 2010 to 2024.
  • L3 Harris Technologies, Inc. /De/ Share-based Payment Arrangement, Expense for the quarter ending March 28, 2025 was $19M, a 26.9% decline year-over-year.
  • L3 Harris Technologies, Inc. /De/ annual Share-based Payment Arrangement, Expense for 2024 was $97M, a 8.99% increase from 2023.
  • L3 Harris Technologies, Inc. /De/ annual Share-based Payment Arrangement, Expense for 2023 was $89M, a 18.3% decline from 2022.
  • L3 Harris Technologies, Inc. /De/ annual Share-based Payment Arrangement, Expense for 2022 was $109M, a 15.5% decline 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 $97M +$8M +8.99% Dec 30, 2023 Jan 3, 2025 10-K 2025-02-14
2023 $89M -$20M -18.3% Dec 31, 2022 Dec 29, 2023 10-K 2025-02-14
2022 $109M -$20M -15.5% Jan 1, 2022 Dec 30, 2022 10-K 2025-02-14
2021 $129M +$35M +37.2% Jan 2, 2021 Dec 31, 2021 10-K 2024-02-20
2020 $94M Jan 4, 2020 Jan 1, 2021 10-K 2023-02-24
2018 $58M $0 0% Jun 30, 2018 Jun 28, 2019 10-K 2022-02-25
2017 $58M +$22M +61.1% Jul 1, 2017 Jun 29, 2018 10-K 2021-03-01
2016 $36M +$3M +9.09% Jul 4, 2015 Jul 1, 2016 10-K 2018-08-27
2015 $33M Jun 28, 2014 Jul 3, 2015 10-K 2017-08-29
2013 $35M +$2.1M +6.38% Jun 29, 2013 Jun 27, 2014 10-K 2016-08-29
2012 $32.9M -$13.2M -28.6% Jun 30, 2012 Jun 28, 2013 10-K 2015-08-31
2011 $46.1M +$10.8M +30.6% Jul 3, 2010 Jul 1, 2011 10-K 2013-08-26
2010 $35.3M Jul 4, 2009 Jul 2, 2010 10-K 2012-08-27
* An asterisk sign (*) next to the value indicates that the value is likely invalid.