这么晚了 顾户 要 还跑去给他送~~ 🍺😃😃 @nabi1214
Signed

Channel
@nabu1223
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
68subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002392394143 |
|---|---|
| Type | Channel |
| Username | @nabu1223 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 2 times, most recently 3 October 2026 |
| On Telegram | t.me/nabu1223 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 91% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 05:35 | 68 | -1 |
| 10 Sept 2026, 12:59 | 69 | -4 |
| 1 Sept 2026, 11:35 | 73 | +1 |
| 24 Aug 2026, 22:43 | 72 | +6 |
| 16 Aug 2026, 15:45 | 66 | -3 |
| 10 Aug 2026, 00:17 | 69 | no change |
| 8 Aug 2026, 11:24 | 69 | -1 |
| 7 Aug 2026, 18:09 | 70 | first reading |
19 posts held, back to 2 December 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 page of 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
14 reactions across 6 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 100.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 7 of the 19 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 2 December 2025 to 8 August 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.
这么晚了 顾户 要 还跑去给他送~~ 🍺😃😃 @nabi1214
Signed
⚡@nabi1214 谢谢顾客们🥰
Signed
谢谢您的支持!收到宝贝后如果有任何问题,请随时联系我们,我们会为您妥善处理。祝您天天开心! @nabi1214 😀⚡
Signed
软中华 😀😀😀😀😀😀 ♥♥♥♥♥♥♥♥♥ 😀下单客服①: @nabi1214 ⚡📱📱📱📱📱📱📱📱 🥰 关注图片频道不迷路:https://t.me/+0g33r11ySG9iZTY1 😀😀😀😀😀😀😀😀😀
Signed
烟种类:木盒1916如意,木盒1916红爆,木盒1916细平安,木盒1916软爆,木盒1916倒插13+7,木盒侠骨柔情粗,木盒细峡谷,峡谷情,奇景,楼外楼,软精品楼,硬精品楼,8°爆珠黄鹤楼,硬红楼,软红楼,软蓝楼,雅香金,天下明楼,木盒硬和天下,木盒细和天下,木盒软和天下,木盒中支和天下,细芙蓉王爆珠,中支芙蓉王,细支小蓝王,蓝芙蓉王,芙蓉王,蓝白沙,三代沙,银白沙,紫云,软玉溪,软云烟,硬1956白塔山,软白塔山,细玉溪,木盒大重九,百年塔,境界玉溪,软小苏,炫赫门,雨花石,木盒红真龙,细九五,红南京,南京十二钗,木盒软九五,细大苏,蓝真龙,白真龙,硬红贵烟,陈皮贵烟,细支白贵烟,翡翠爆珠,阿里山,木盒中支翡翠,经典绿熊猫,硬中华,软中华3字头,软中华2字头,双控中华,细小金中,软红牡丹336,软红牡丹333,礼盒方金中支,硬荷花,细木荷花,中支荷花,木盒软荷花,好日子礼炮,软经典,盒01典,1906双喜,硬经典,金五叶神…
Signed
😃招聘部门助理🩳🥫🚵♀️ 要求: 中国外籍都可,会做表格,有过助理工作经验或财务工作经验优先 年龄18-25 底薪 1200转1500😊 🥎🍝 南海隔壁 联系: @nabi1214
Signed ·
#柬埔寨流量开通攻略(完整版) 红卡/黄卡/绿卡/蓝卡都有了! 一、Metfone(红卡) ● 查询流量余额:拨打*1535097#或*1201#。 ● 开通流量套餐: ○ 1.5美元/7天:15GB流量,拨打*1535*15#。 ○ 6美元/30天:60GB流量,拨打*1535*60#。 ○ 10美元/30天:100GB流量,拨打*1535*10#。 ○ 1美元/7天:5GB流量,拨打*1535*1#。 ○ 1.5美元/7天:5GB流量+社交媒体流量(Facebook、WhatsApp等),拨打*1535*2#。 ○ 1.5美元/7天:5GB流量+娱乐流量(YouTube、TikTok等),拨打*1535*3#。 二、Smart(绿卡) ● 查询流量余额:拨打*1201#或*030888#。 ● 开通流量套餐: ○ 1.5美元/7天:10GB流量,拨打*1710*150#。 ○ 6美元/30天:60GB流量,拨打*17…
❤3
Signed - 安然
😃招聘部门助理🩳🥫🚵♀️ 要求: 中国外籍都可,会做表格,有过助理工作经验或财务工作经验优先 年龄18-25 底薪 15000转18000😊 🥎工作11小时 休2天🍝 凯博2 房补200美金 联系: @nabi1214
❤1
Signed - 安然
2️⃣🔤2️⃣8️⃣ 体育 招人事~ 快来 欢迎🎉 岗位:招聘 🚲 薪资待遇:10k-12k+高额提成 上班 : 9休息 4 ~ 很自由 😃 性别:不限🧩🏀 国籍:不限 工作地点:南海 🤦 📱 联系 : @nabi1214
Signed - 安然
2026❤️ 新年快乐🎆
Signed - 安然
2️⃣🅾️2️⃣8️⃣ 体育直招⚾️ ✈️ 上班地点: 😊 南海☺️ 联系✈️: @nabi1214 👍岗位:【推广部】 薪资⚓️ 底薪10000转正 12000RMB +高提成, ⚾️月休4个半天 或者 休2天🏈 🛑岗位【人事部】 薪资10k-12k+提成+房补🧩 上班9 休息4 ~很自由 岗位 🍕【后台客服】🪝 薪资薪资待遇:10000RMB 转正12000RMB😀 KPI绩效:1000-5000RMB 全勤奖:500RMB🛺 🚲上班9小时,三班倒;月休2天有满勤。休息2天+则无满勤🧩 😀 风控 ~~~ 😃 维护~~~ 🏊♂️ 助理~~~~ 🍣 网管~~ 🌭🌭🌭🌭🌭🌭 有接赔付 😅📱联系: @nabi1214
❤4
Signed - 安然
岗位:推广专员 薪资待遇 10000+提成10-15% 12小时,月休2 【平均三五万,月薪十万大有人在,因团队很多人赚钱了,都打算上岸,所以急需推广补缺,天推, 虽然上班时间12小时,但是工作强度不是很高,大部分时间还是在看直播研究推单技巧】 岗位职责 思路清晰,有想法,懂得团队协作。最好有自己的渠道,会开发,引流,懂得吸引客户 岗位要求 配合团队工作,要坚持,遇到困难要迎刃而解,有交流,有担当,有推广经验优先,服从上级安排,性格开朗。 小白:听话,有上进心,善于学习,有培养价值 推广开发提成算法: 比如100万净盈利,减去资源费(正常每月花费再5-10万),减去彩金费用(每个月1-2万的样子),减去微信工具费 (5左右)剩下的钱,乘以15点就是你的提成 100万例:(100万-5万-1万-5千=93.5万) 935000*15=140250提成 底薪10000+提成140250=150250 联系: @nabi12…
Signed - 安然
Showing the 12 most recent of 19 posts we hold for @nabu1223. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“生活小日常直招🥀🎊” (@nabu1223), 68 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/nabu1223.
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.