I suspect that either the rows got deleted or insert statements were done that incremented the counter but they were in a transaction that was then rolled back.
Looking at this related answer, it looks like it could also be caused by SQL Server caching future identity values and then getting restarted before it has had the opportunity to use them.
Identity increment is jumping in SQL Server database
