SHARK.IO PLAY ON POKI

Sources and how we check facts

A fact needs two independent public pages before I treat it as settled. One page means the status column says “1 source.” A clash stays a clash.

Shark.io key art from the Poki CDN, one of the primary sources
Image credit: PEGASUS / Poki.
Maneater capsule from Steam, a store page used as a source
Image credit: Maneater / Steam.

What I open first

Store and publisher pages come first: Poki, Steam, Google Play, the App Store, Roblox, Ubisoft, and a studio’s own product page. Wikis come next, then portal pages, then a YouTube title, description or frame when the video is the only public look at a delisted game. I name the page at the bottom of each article and I date the check. The date used across this edition is 10 November 2026.

Conflicts I refused to merge

Hungry Shark Evolution’s wiki body says 18 October 2012 and its infobox says 24 October 2012. Hungry Shark World’s article says four locations and a menu says five. Sharkosaurus Rampage’s Poki metadata says Gametornado and a FAQ on that page says Damp Gnat Games. The SharkBite 2 table keeps only 300K and 400M from an official Abracadabra post; Beebom independently lists 300K. Depth’s historical developer and current store credit describe different ownership periods. Each article prints both.

FAQ

How are codes checked?

Codes are matched to an official public announcement and compared with independent public lists. The status column counts sources and a missing code is not automatically marked expired.

What if a number is missing?

The cell stays blank. I do not estimate map counts, file sizes or gem prices.

Related

Sources