post_event_list contains ALL events (including Adobe Standard Events, Instance of eVars, and your Custom Events)... as such, the numbers you see in the list do not correspond to your events.
With your Raw Data Feed, you should get an Events.tsv file that will show you what the numerical value in the list corresponds to.
As a general note, standard events are the lower numbers, "Instance of eVars" start at 100 (i.e. 100 is "Instance of eVar1", 101 is "Instance of eVar2", etc - note, there are some other reserved values in the Instance of eVars, so around Instance of eVar101 the number jumps to 10000), Custom Events start at 200 (i.e. 200 is "event1", 201 is "event2" - the same jump happens like above when you hit "event101" the number jumps to 20100), etc...
In order to properly process the data, you must use the mapping file provided with your feed, you can't just look at the list and use the data as provided... "24" is not "event24" (I don't know what it is... offhand)
Unless you mean there is no "24" listed corresponding to an event (but given you next statements, it doesn't seem like you are using your mapping file... as 20100-20999 should be events 101-1000)... if you are sure that this is the exact data (and not an ETL issue taking the data feed and processing it into your data base), then you may have to reach out to client care and ask why "24" isn't mapped.
I have never seen multiple instances of "000"... check your mapping file, does "000" correspond to an event in your list... maybe on those hits, that specific event is being sent multiple times? This could also be an ETL issue... I would double check and confirm that the data is being processed correctly (just to be safe)
