Channel
@TG33220
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
18subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001944379103 |
|---|---|
| Type | Channel |
| Username | @TG33220 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/TG33220 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 19:17 | 18 | no change |
| 14 Aug 2026, 22:32 | 18 | first reading |
17 posts held, back to 23 February 2024 — 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 17 posts for this entry, the most recent from 5 May 2026. An engagement rate over an empty window would be a number about nothing.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👎 | 1 | 50.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 23 February 2024 to 5 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔹正规综合体育盘 🔹公司不禁足，年终奖13薪，半年假，🧧生日年节假日有红包🧧 🔹公司包吃住 招聘岗位（基础岗位） 📢 推广 / 运营类 #推广专员 / 推广团队 #新媒体运营专员 #活动执行专员 #商务拓展专员 #商务专员 #运营专员 #自媒体运营 #🧑💼 客服 / 维护类 #客服专员（轮班） #代理维护专员 #内账专员 #签证专员 #签证账目专员 #医疗接机专员 #📊 风控 / 数据类 #风控专员 #审计专员 #数据分析师 #统筹专员（财务数据类） #🧾 行政 / 职能类 #行政专员 #行政助理 #后勤专员 #后勤助专员 #部门助理 / 小组助理 #人资专员 #💰 财务 / 账务类 #资产专员 #账目管理专员 #账目专员 #出纳/账务相关岗位 📞 销售 / 招商类 #招商专员 #招商组长 🎯 其他基础岗位 #UI专员 #网络专员 #网络工程师 #法务公关代表 #JZ专员 #牌照管理专员 #代理客服专员 #培训专员 #薪酬专…
https://t.me/MK888bot?start=21690364_B 点击就能玩的游戏。快来试试吧☺️☺️☺️
欢迎进群来玩： @OGFoo1
求职发财联系笨蛋美女🪽🥺🪽 迪迪：@asa999
🐰🌷🌿🏠🌻🐊我知道，你绝不简单，如果你和现在的工作没得聊，那就来我这聊聊！你就是我最需要的人才，而我正是你苦苦等待的伯乐👍🍋💖🍪🌳 求职发财联系笨蛋美女🪽🥺🪽 迪迪：@asa999 米其林：@Michlinxx 发财岗位详情： @dibaizhizhao888 @asa999ZPZX 特殊岗位特殊对待，福利待遇天花板！！🌙
❤1
TG33220风筝导航指南 pinned «✅ IOS限制解除 ✅TG语言包 ✅ TG双向解除 ✅ 听歌机器人 ✅ 群管理机器人 ✅ 注销TG账号 ✅ TG安全守则 ✅ TG电脑多开 ✅ TG两步验证 ✅ TG机器人创建 ✅ TG假冒盗号 ✅ TG创建贴纸 ✅ 招商代理软件 ✅ 虚拟币钱包教程 ✅ 免费高速VPN 👍 菲律宾外卖 …»
文字版简历录用登记: 一 , 姓名（代号）: 性别: 民族: 出生日期: 户籍所在地: 婚姻状况: 身高: 体重: 最高学历： 外语程度: 出国经历: 护照有效期: 邮箱： 备用联系方式： 二, 教育经历: XXX年-XXX年 毕业学校: 专业: 学历: 三, 工作经历: XXX年-XXX年 XXX年-XXX年 XXX年-XXX年 四: 自我介绍:
💓招商专员 💓 推广专员 💓 招聘专员 💓 招聘组长 💓招商部长 💓 海外招商 💓 商务接待 💓 会计专员 💓新媒体运营专员 💓公关专员 💓运营专员 💓商务助理 💓运营执行 💓英语商务 💓法务公关 💓逆向开发工程师 💓行政专员 💓推广专员 💓业务专员 💓厨师 💓吉隆坡助理 💓菲律宾助理 💓吉隆坡司机 💓客服专员 💓出纳专员 💓后勤专员 💓推广助理 💓报告编辑 💓代理发展专员 💓代理发展组长 💓监测专员 💓初级UI 💓文案专员 💓统筹财务专员 😉【BOSS直聘】： 😱@asa999😱 👍赔付透明 /包机票 🥳提供迪拜合法的白产工作签 点这里 迪拜直招 🔙返回主页
https://t.me/boost/xinwennx
Voice message, posted without a caption
新来的台湾小姐姐 人美声甜 期待你的到来
➡️招商代理推荐使用聊天软件，推荐指数按照顺序排名（国内可用）⬅️ letstalk https://www.letstalk.net/downld yeechat https://yeechat1.com/ cloudchat（CC安卓手机下载） https://www.cloudchat.com/ 泡泡Mosgram https://ya.cn/index.html Skype（安卓手机下载） https://www.skype.com/en/thank-you-skype/ telegram(国内请使用VPN） https://telegram.org/dl/desktop/win64_portable 土豆聊天 https://download.dllcpt.org/win/Potato_Desktop2.37.zip 蝙蝠聊天 https://dl.baticq.com/pcbatchat.exe ➡…
👎1
Showing the 12 most recent of 17 posts we hold for @TG33220. 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 — 949,776 of 1,481,217entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@TG33220 named 2 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“TG33220风筝导航指南” (@TG33220), 18 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/TG33220.
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.