last modified rows timestamp for SQL Server 2016
Noting done by default. You can turn on stuff like temporal (probably overkill) or create a trigger to update the table.
SQL Server keeps track of all modification internally, in the transaction log, for its own purposes (like rollback and crash recovery). But the log is volatile and even if you get there before the info is gone, you'd have to decode the info yourself using unsupported means (like fn_dblog).
[Edit] Adding in the options Change Tracking (lower overhead) and Change Data Capture (higher overhead and uses an Agent job but gives more info than CT), as suggested in the comments below by Dominique.