G.MEDIA press kit

Live figures (catalogue, archives, bots and our own channels) update automatically. The ad network and Cloudflare figures are snapshots we re‑measure by hand; the date is on each card. We round down: “+” marks a floor, “≈” an average over a period.

• Ad network — subscribers of the owned and partner Telegram channels in the G.MEDIA sales catalogue, from public t.me pages. The catalogue as of April 5, 2026 lists 211 channels; 19 links no longer lead to a channel and are not counted, which leaves 192. A channel with two usernames is one channel; audiences shared between channels are not de‑duplicated: 63,622,387.
• Bots and own channels — Telegram's “monthly users” counter of our bots (rolling 30 days) plus subscribers of our own channels. It is a sum of counters, not a count of people: someone in two channels and a bot counts three times. Total: 6,138,570.
• Requests and domains — Cloudflare, 7 full UTC days, October 11–17. Requests average 56,763,268 a day, lower on some days. This is infrastructure load, not people: about 40M of it is PostBot and Wall service traffic over APIs and webhooks, and about 22% are blocks (403) and errors (5xx). Domains are those with at least one request in the week: 472 of 523.
• Countries — Cloudflare Web Analytics over the same 7 days: only browsers that ran JavaScript, at least one visit from the country.
• Catalogue and archives — public counters on tg.me and the open tgadsspy.com API, refreshed every 5 minutes. tg.me prints large counters rounded to one decimal, so half a unit of the last digit is taken off such a figure before rounding down. Views are on posts of other channels in the archive, not G.MEDIA's audience.
• Products — entries in the g.media product registry marked live or open beta.
• Wall — all‑time registered members, not active users.