useradd only uses the same UID and GID when either:
It will skip over already-in-use IDs. So, I would guess that you have added other users and/or groups since you created those that have matching UID/GID pairs.¹
To get the IDs back in lock-step, you could create the next one with -g and -u flags to give it IDs equal to one past the highest UID and GID yet assigned. Subsequent useradd calls won't fill the gaps back in. They'll just start numbering past the new high-water mark.
There's nothing wrong with having desynchronized UID and GID values. The system will work perfectly fine in that condition. Old-style Unixes generally didn't use a group-per-user scheme, so that the IDs were never synchronized from the start at all.
Footnotes:
- You probably did not do this interactively. Many packages add groups, and sometimes users, in order to constrain access to files and other facilities owned by that package. Usually they do this with OS-reserved group IDs below 1000, but not always. When they add a group but not a user, it desynchronizes the two sets of ID values.