成吉思汗 加密中心 (Genghis khan Crypto Hub) pinned a photo

Channel
成吉思汗 加密中心 (Genghis khan Crypto Hub)
@GenghishhanCalls
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
512subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001522542784 |
|---|---|
| Type | Channel |
| Username | @GenghishhanCalls |
| Description | 分析和推荐即将进行的预售、发射和白名单的新币社区。 在社区和频道同步推广。 埋伏上顶级交易所的老币。 (信息参考,不作为投资建议) 币道社区 https://t.me/GenghishhanCalls 📲 商务联系: @Genghishhan |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GenghishhanCalls |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 05:32 | 512 | no change |
| 7 Aug 2026, 05:22 | 512 | first reading |
Engagement
20 posts held, back to 20 April 2025 — the 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 20 posts for this entry, the most recent from 11 June 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈2,140
- Videos
- ≈57
- Links
- ≈2,410
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
ETH 联合创始人 CAT CUDDLES 约瑟夫·鲁宾 合约ETH: 0x90fD0CD338a2a9d61e40dcA7122b58a375Dba989 电报: https://t.me/Cuddleserc 我们提供的任何内容均不构成财务建议,纯属信息分享,请做好自己的考察并对自己的投资负责
成吉思汗 加密中心 (Genghis khan Crypto Hub) pinned a photo
Mirai 确认的狐狸名字 合约ETH: 0xf78E87F183c15a5f526d796c1bea9E9C3643b327 电报: https://t.me/hamtaroerc20 推特: https://x.com/hamtarotoken 我们提供的任何内容均不构成财务建议,纯属信息分享,请做好自己的考察并对自己的投资负责
成吉思汗 加密中心 (Genghis khan Crypto Hub) pinned a photo
奥马利是青蛙佩佩 (Pepe the Frog) 的创造者马特·弗里 (Matt Furie) 心爱的宠物猫。 合约ETH: 0x90001c5F2C6fFD4B90A801AfDDEfcbf31965c667 电报: https://t.me/OmalleyToken 推特: x.com/OMalleyToken 网站: https://omalleytoken.com 我们提供的任何内容均不构成财务建议,纯属信息分享,请做好自己的考察并对自己的投资负责
成吉思汗 加密中心 (Genghis khan Crypto Hub) pinned a photo
链上第一只KEN 我们在Kabo-chan之前养的那只狗。它是主人(佐藤敦子)的第一个DOGE,也是$KEN的开端。 合约ETH: 0xf4c492Cbc2e73B251042264Faa953c8c7a53c1a2 电报: https://t.me/Kenogcto 推特: https://x.com/kenogcto 我们提供的任何内容均不构成财务建议,纯属信息分享,请做好自己的考察并对自己的投资负责
成吉思汗 加密中心 (Genghis khan Crypto Hub) pinned a photo
来认识一下真正的瑰宝——表情包币 $PAPAM 。它将改变一切。随着教皇的不幸离世,世界即将走向终结,拯救一切的是埃隆·马斯克的星际飞船团队,他们将殖民地球,拯救人类的重要成就。加密货币 $PAPAM 即将上线,敬请关注。🪙 CA:0xCc927642EA496B15CaF677734070f0316Df59054 TG:https://t.me/habemus_papam_BSC X:https://x.com/PapamHabemus 网站:https://papamhabemus.com/
成吉思汗 加密中心 (Genghis khan Crypto Hub) pinned a photo
所有 degens(加密、扑克、体育博彩)竞争的场所。 合约SOL: CLyhG2aVrnvbxXAXokBGvKjmNfsamPKtGW4Gu9AHpump 推特: https://x.com/wsod_sol 网站: https://wsod.io 我们提供的任何内容均不构成财务建议,纯属信息分享,请做好自己的考察并对自己的投资负责
Showing the 12 most recent of 20 posts we hold for @GenghishhanCalls. 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.
Mentions
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
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@GenghishhanCalls 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“成吉思汗 加密中心 (Genghis khan Crypto Hub)” (@GenghishhanCalls), 512 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/GenghishhanCalls.
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.