Metallus 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
Metallus Inc. quarterly/annual Share-based Payment Arrangement, Expense history and growth rate from 2012 to 2023.
  • Metallus Inc. Share-based Payment Arrangement, Expense for the quarter ending June 30, 2024 was $3.5M, a 20.7% increase year-over-year.
  • Metallus Inc. Share-based Payment Arrangement, Expense for the twelve months ending June 30, 2024 was $13M, a 30% increase year-over-year.
  • Metallus Inc. annual Share-based Payment Arrangement, Expense for 2023 was $11.5M, a 30.7% increase from 2022.
  • Metallus Inc. annual Share-based Payment Arrangement, Expense for 2022 was $8.8M, a 20.5% increase from 2021.
  • Metallus Inc. annual Share-based Payment Arrangement, Expense for 2021 was $7.3M, a 10.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 $11.5M +$2.7M +30.7% Jan 1, 2023 Dec 31, 2023 10-K 2024-02-28
2022 $8.8M +$1.5M +20.5% Jan 1, 2022 Dec 31, 2022 10-K 2024-02-28
2021 $7.3M +$700K +10.6% Jan 1, 2021 Dec 31, 2021 10-K 2024-02-28
2020 $6.6M -$800K -10.8% Jan 1, 2020 Dec 31, 2020 10-K 2023-02-24
2019 $7.4M +$100K +1.37% Jan 1, 2019 Dec 31, 2019 10-K 2022-02-24
2018 $7.3M +$6.6M +943% Jan 1, 2018 Dec 31, 2018 10-K 2021-02-25
2017 $700K -$100K -12.5% Jan 1, 2017 Dec 31, 2017 10-K 2018-02-20
2016 $800K -$6.2M -88.6% Jan 1, 2016 Dec 31, 2016 10-K 2018-02-20
2015 $7M +$1M +16.7% Jan 1, 2015 Dec 31, 2015 10-K 2017-03-16
2014 $6M +$3.2M +114% Jan 1, 2014 Dec 31, 2014 10-K 2017-03-16
2013 $2.8M +$200K +7.69% Jan 1, 2013 Dec 31, 2013 10-K 2016-02-29
2012 $2.6M Jan 1, 2012 Dec 31, 2012 8-K 2016-01-08
* An asterisk sign (*) next to the value indicates that the value is likely invalid.