Telegram RegisterThe public register of Telegram

Channel

🏆MK官方频道🏆

@mkgf8888

On this record: Growth · Engagement · Posts · Citations · Cite this entry

141subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002131657884
TypeChannel
Username@mkgf8888
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/mkgf8888

Growth

1419 Aug 2026, 15:17 — 141 subscribers9 Aug 2026, 20:11 — 141 subscribers9 Aug 2026, 15:179 Aug 2026, 20:11
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 140–142 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 20:11141no change
9 Aug 2026, 15:17141first reading

Engagement

17 posts held, back to 17 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 Jun 2026, 10:25 UTC14 viewsread 9 August 2026
Photo

🏆 今晚世界杯焦点大战🏆 🇧🇷 巴西 VS 🇯🇵 日本 🔥 强强碰撞,机会就在这一场! 🇧🇷 内马尔领衔巴西? 🇯🇵 还是支持日本爆冷? ⚽️要pei率的,私我⚽️ 私信: @ganfanxi666

14 Jun 2026, 15:06 UTC19 viewsread 9 August 2026
Photo

【世界杯C组积分榜:苏格兰小组第一!摩洛哥与巴西分列第二和第三】 世界杯C组小组赛首轮,巴西1-1摩洛哥,海地0-1苏格兰。 目前C组积分榜上,苏格兰3分小组第一!摩洛哥与巴西分列第二位和第三位,海地垫底。 巴西2张黄牌,摩洛哥0黄牌,因此摩洛哥排名靠前。 MK体育飞投版官方频道:点击进入 合作:球速总裁 @ganfanxi666

11 Jun 2026, 07:17 UTC789 viewsread 9 August 2026
Photo

【韩国队世界杯号码:孙兴慜7号、李刚仁19号、朴镇燮16号】 韩国足协官方公布世界杯球员号码 金玟哉4号、孙兴慜7号、李在城10号、李刚仁19号、朴镇燮16号。 MK体育飞投版官方频道:点击进入 合作:球速总裁 @ganfanxi666

11 Jun 2026, 07:12 UTC15 viewsread 9 August 2026
Photo

综合-6月12日热门赛事时段分布图】 MK体育飞投版官方频道:点击进入 MK体育—飞投:MK.bet 合作联系;球速总裁 @ganfanxi666

11 Jun 2026, 06:55 UTC15 viewsread 9 August 2026
Photo

下注网址 http://mkty712.com 🌸🌸🌸希望大哥 好运连连 盈利不断! 🌸🌸🌸

11 Jun 2026, 06:54 UTC15 viewsread 9 August 2026
Photo

世界杯第一场比赛早盘墨西哥vs南非已经可以下注了 https://t.me/MK888bot?start=34855140_B

9 Jun 2026, 11:24 UTC15 viewsread 9 August 2026
Photo

https://t.me/MK888bot?start=34855140_B 大佬们帮忙打个新增

Showing the 12 most recent of 17 posts we hold for @mkgf8888. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 284,169 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 9 August 2026 — this entry's latest reading, not the date you are reading this.

“🏆MK官方频道🏆” (@mkgf8888), 141 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/mkgf8888.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.