@ Blackcrusader: That chain count is typical of public table1 + table2 merged, so I'm confident your table has ~28.5 billion chains / file size ~341GB.
File length: 3015 MByte At 30Mbps that's around 15 minutes of recording.
ASIASAT 5 100.5E 3860 V 30000 40 second recording......
TS file: C:\Users\STADIUM\Desktop\100.5E_3859.785_V_30000_(2021-04-14 14.14.15)_dump.ts
Using PID: 401
Using file limit: 4096 MByte
File length: 317 MByte
UsingFileLen: 332756240 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 191h B8h-Crypt8:66 4E B1 36 15 8C 88 12 [E] Count:116314
PID: 191h B8h-Crypt8:00 8A 84 9D C7 71 DB EB [E] Count:68
PID: 191h B8h-Crypt8:00 93 BA A1 1B A9 B1 15 [E] Count:68
PID: 191h B8h-Crypt8:00 F4 E0 1B 5A BB 68 E9 [E] Count:68
PID: 191h B8h-Crypt8:01 3A AC F3 D3 AF E8 71 [E] Count:68
PID: 191h B8h-Crypt8:01 AC C7 24 6E 00 F1 0B [E] Count:68
PID: 191h B8h-Crypt8:02 3B CD D2 F2 03 15 3B [E] Count:68
PID: 191h B8h-Crypt8:02 DF F9 10 C5 BE 38 65 [E] Count:68
...
Time for searching Crypt8 = 0 sec.
Search CW Start
RBT file: D:\Biss V1 file\B8hxFFh\B8hxFFh_table2\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 217891 possible chains (harddisk only search time = 97 sec.)
Of course every time a TS stream is recorded we get different results for the tables counted and speed used.