🔥 20.3x $CAYENNE 💰 $111.2K ➜ $2.3M MC 🦜 PIRBView (Pro) 🎯 Maestro · Maestro Pro 🔕 /alerts — pause milestone alerts

Channel
太初链纪 $GCC
@GenesisChainLog
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
15,764subscribers
+3,603 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002518629852 |
|---|---|
| Type | Channel |
| Username | @GenesisChainLog |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/GenesisChainLog |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 01:37 | 15,764 | +4,722 |
| 5 Sept 2026, 19:56 | 11,042 | -125 |
| 3 Sept 2026, 20:36 | 11,167 | -201 |
| 2 Sept 2026, 10:12 | 11,368 | -264 |
| 1 Sept 2026, 11:17 | 11,632 | -468 |
| 31 Aug 2026, 13:05 | 12,100 | -951 |
| 30 Aug 2026, 11:11 | 13,051 | -499 |
| 29 Aug 2026, 13:57 | 13,550 | -347 |
| 28 Aug 2026, 13:03 | 13,897 | -193 |
| 27 Aug 2026, 12:15 | 14,090 | -65 |
| 26 Aug 2026, 09:41 | 14,155 | +4,698 |
| 23 Aug 2026, 14:25 | 9,457 | -277 |
| 19 Aug 2026, 23:15 | 9,734 | -296 |
| 18 Aug 2026, 20:08 | 10,030 | -214 |
| 17 Aug 2026, 19:48 | 10,244 | -238 |
| 16 Aug 2026, 17:48 | 10,482 | -340 |
| 15 Aug 2026, 00:14 | 10,822 | -147 |
| 13 Aug 2026, 17:57 | 10,969 | -152 |
| 12 Aug 2026, 18:03 | 11,121 | -108 |
| 11 Aug 2026, 20:35 | 11,229 | first reading |
Engagement
96 posts held, back to 30 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 43 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.6%
- avg views ÷ 15,764 subscribers
- Avg views / post
- 2,460
- 74 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 75
- of 96 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 96 (30 July 2026 – 2 September 2026) |
| Views total | 181,918 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:45 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
✅ 3.0x $COIN 💰 $124.3K ➜ $367.7K MC 🦜 PIRBView (Pro) 🎯 PIRBX · Maestro · Maestro Pro 📈 SG 🔕 /alerts — pause milestone alerts
$GYATT 热度正在快速升温,强势资金持续涌入,市场关注度不断攀升。依托 $RBLX 生态叙事与社区热度,项目短时间内已经展现出强劲的爆发力。 交易活跃度持续增加,买盘与资金流动十分强势,越来越多交易者开始关注这个新兴机会。随着社区不断扩张,市场情绪持续升温,$GYATT 的故事才刚刚开始。 🔥 热度聚集,资金关注,社区正在形成。$GYATT 值得持续关注。 🦅: https://dexscreener.com/robinhood/0xf96ba0a62d77c0b99811613a43a7badd892c2ef0ded74f83a3f7359ccf2c7d79
✅ 4.2x $BOB 💰 $117.8K ➜ $493.6K MC 🦜 PIRBView (Pro) 🎯 Maestro · Maestro Pro 🔕 /alerts — pause milestone alerts
✅ 2.0x $GYATT 💰 $94.9K ➜ $191.0K MC 🦜 PIRBView (Pro) 🎯 Maestro · Maestro Pro 🔕 /alerts — pause milestone alerts
🔮 @Genesischainlog KOL Hit 2X+ $SYNDICATE SOL play called at $379.2K market cap. Current Market Cap stands at $761.3K. Clean execution. 🔮 $379.2K 🔮 $761.3K 🔮MAE 🔮KOL 🔮BOT
羽毛兄弟强势来袭,Solana Meme 生态新势力正在快速升温! $FBROS 以独特的鸟类兄弟叙事吸引市场关注,短时间内交易活跃度持续上升,买盘明显强劲,社区热度不断扩散。流动性充足,市场关注度快速提升,越来越多玩家开始加入这场属于 Feather Bros 的狂欢。 不同的鸟,同一个阵营。 Different Birds, Same Flock. $FBROS 正在成为 Solana 生态值得关注的新 Meme,热度才刚刚开始。 📊: https://dexscreener.com/solana/Bc41Ped2cpQyzFvFUzsTN9Rkq3Ggcsav4JjGyYfLWdvr
5EHz51kdjgqmq7SH287DihsKZ2GkjziWLUpfpdrVpump
25人刚刚在metawin的25万美元比赛中得到了一个胖包 10万美元到第一名,5万美元到第二名是疯狂的。 如果你上个月错过了,这个月你还有另一个机会,因为他们将再向活跃玩家发放100万美元的奖金 每天在metawin.com上存款并登录,以获得这些奖励 如果你真的在那里活跃,你不可能不赢得一些东西
Accomplishment Unlocked: x4! 🖖 @GenesisChainLog made a x4+ call on OTC🟣 $1.6M ➡️ $6.4M 👁 View Call 📊 View Stats 👤 KOL 📢 Advertise here
$NICKGPRO 正在 Solana Meme 生态快速升温,短时间内吸引大量市场关注。 交易活跃,买盘强劲,资金持续流动,社区热度不断扩散。随着越来越多玩家加入,$NICKGPRO 的市场关注度正在持续提升。 Solana Meme 新热点正在形成,$NICKGPRO 后续表现值得持续关注。 DYOR,关注市场动态,把握市场机会。 ❌: https://x.com/nickgpro_x ✈️: https://www.nickgpro.site/
Accomplishment Unlocked: x3! 👌 @GenesisChainLog made a x3+ call on NICKGPRO🟣 $678K ➡️ $2.1M 👁 View Call 📊 View Stats 👤 KOL 📢 Advertise here
Showing the 12 most recent of 96 posts we hold for @GenesisChainLog. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@GenesisChainLog named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 30 August 2026 – 30 August 2026 · confirmed gone 3 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 September 2026 — this entry's latest reading, not the date you are reading this.
“太初链纪 $GCC” (@GenesisChainLog), 15,764 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/GenesisChainLog.
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.