Telegram RegisterThe public register of Telegram
Telegram profile photo for 夏夏北部精選

Channel

夏夏北部精選

@bxx328

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

255subscribers

+16 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002534908393
TypeChannel
Username@bxx328
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live2 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/bxx328

Topic

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

2392552478 August 2026 — 239 subscribers8 August 2026 — 239 subscribers15 August 2026 — 240 subscribers23 August 2026 — 243 subscribers31 August 2026 — 245 subscribers10 September 2026 — 248 subscribers18 September 2026 — 253 subscribers2 October 2026 — 255 subscribers8 August 20262 October 2026
8 measurements spanning 56 days, net +16. 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 237–257 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 23:19255+2
18 Sept 2026, 22:58253+5
10 Sept 2026, 04:59248+3
31 Aug 2026, 02:23245+2
23 Aug 2026, 04:58243+3
15 Aug 2026, 10:07240+1
8 Aug 2026, 09:50239no change
8 Aug 2026, 07:16239first reading

Engagement

12 posts held, back to 5 August 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 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 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 06:13 UTC6 viewsread 8 August 2026
Photo

茶客夏|88發發節 開跑 一年只有一次!福利拉滿🔥 💥全場指定方案 88折起 🎁消費即送 $8,888 現金優惠券包 🏆8/8前消費前三名可得現金回饋 🥇888元|🥈666元|🥉333元 ⏰每日晚上 20:00 前完成消費 ✨正價妹妹不限節數享 8折優惠 🎁前8位完成預約 送限定驚喜禮包! 👑單節實付滿 8K 直接送永久8折 💎熟客累積消費滿8K 送正價妹5折×8次 🏅活動期間累積消費8節或直接8節方案 👑立即升級最高等級 VIP 🌟再送 $88,888 現金優惠券 ━━━━━━━━━━━━ ⚠️福利名額有限,部分優惠限量發送,送完即止。現在預約,不只是省這一次, 而是把接下來好幾個月的優惠帶回家‼️ 活動參與聯絡⤵️ ⚡️TG:@ttw226 ❤️Gleezy💬LINE:tw226

7 Aug 2026, 14:39 UTC21 viewsread 8 August 2026

最近盜號以及各種詐騙橫行 已看到不少人的賬號變成不是自己的。 夏夏在這邊做一個~減少被盜風險的防範 [不保證一定不會,但是可以保險一些] https://t.me/Line_tw226/143 詳情點擊⤴️即可查看

7 Aug 2026, 14:39 UTC21 viewsread 8 August 2026

為了避免你我賬號某天突然不在自己手上 還請可以多多加入夏夏的官方論壇 www.tw226.com 以做備用🙏 夏夏賬號不見會第一時間公告在論壇裡‼️ 你們賬號不在也可以透過論壇找到夏夏‼️

6 Aug 2026, 14:16 UTC37 viewsread 8 August 2026

JVID私密寫真模特偷下海~ 💰15K一節 🉑無套 📍#雙北推薦 有想法的來密我 @ttw226

6 Aug 2026, 02:09 UTC38 viewsread 8 August 2026

新的一天開啟了! 今天正妹很多! 密我一夏了解更多正妹資訊! https://t.me/ttw226

5 Aug 2026, 15:33 UTC32 viewsread 8 August 2026
Forwarded from @xi328Photo

剛剛有一個 2023 年就跟我約過的老顧客重新找到我 他今天剛好出差,想找個時間放鬆一下 但又一直卡在猶豫不決。 一問才知道,他之前遇到了很不負責任的不良總機 打槍之後房間被轉接騷擾甚至威脅 搞得他現在心有餘悸,非常害怕給房號。 說真的,夏夏非常理解哥哥們曾經被劣質同行傷害過的戒備心。 他是我的熟客,我當然相信他的為人,我也確定知道他肯定是有開好房間的,但我手底下出勤的妹妹們,並不清楚你是什麼樣的為人跟處事風格,對於一切來說 跟古代的盲婚啞嫁沒有區別。 💡為什麼夏夏堅持一定要有確切房號才安排出發? 這是對妹妹人身安全最基礎的保障: 妹妹們獨自出門,一個明確的房號是她們唯一的安全屏障,也是證明哥哥確實入住、真的有誠意安排的憑證。 誠意不是口頭說說而已: 我們沒辦法只憑一句:我真的在房間了、真的開好了 就直接讓妹子盲目跑一趟。 有了確切房號,大家安排起來都踏實,也不浪費彼此的時間。 🛡夏夏的保證與原則 絕對誠信,守口如瓶…

5 Aug 2026, 10:36 UTC34 viewsread 8 August 2026

歡歡客評新增⤵️點擊可看 -撕裂白絲狂肏,深情舌吻射到爆

5 Aug 2026, 06:09 UTC33 viewsread 8 August 2026
Photo

🎀 甜甜:156/C/45/21歲 台北大學在校生,小隻翹臀很好抱☺️ 俏皮活力個性,女友感足,什麼都配合你 #雙北10K ⭐茶客夏公告區😻 t.me/Line_tw226 𓆩點擊藍色字體看各地𓆪 [北部] [中部] [南部] ❦客評查看 t.me/kpinp 🦋🪽🪽🪽🧸🖤🦋🖤🦋 🌐LINE預約 tw226 🌐TG預約 @ttw226 ⭐Gleezy預約 tw226 🔅論壇: www.tw226.com

5 Aug 2026, 06:09 UTC33 viewsread 8 August 2026
Photo

🎀 奶昔:165/D/47/25歲 溫柔鄰家的幼稚園老師,膚白勻稱有C杯 溫柔撒嬌搭配甜蜜互動很舒服,不會冷場☺️ 會主動親親舔舔,乾淨無異味雞雞她最愛 #新竹6000 ⭐茶客夏公告區😻 t.me/Line_tw226 𓆩點擊藍色字體看各地𓆪 [北部] [中部] [南部] ❦客評查看 t.me/kpinp 🦋🪽🪽🪽🧸🖤🦋🖤🦋 🌐LINE預約 tw226 🌐TG預約 @ttw226 ⭐Gleezy預約 tw226 🔅論壇: www.tw226.com

5 Aug 2026, 06:09 UTC38 viewsread 8 August 2026
Photo

🎀 星空:158/E/48/23歲 看似單純無害,私下超懂玩超會玩! 純慾貪玩路線,讓你不自覺想要探索更多 大方熱情個性,怎麼玩都好玩,全程配合度超高 #雙北12K ⭐茶客夏公告區😻 t.me/Line_tw226 𓆩點擊藍色字體看各地𓆪 [北部] [中部] [南部] ❦客評查看 t.me/kpinp 🦋🪽🪽🪽🧸🖤🦋🖤🦋 🌐LINE預約 tw226 🌐TG預約 @ttw226 ⭐Gleezy預約 tw226 🔅論壇: www.tw226.com

5 Aug 2026, 06:09 UTC32 viewsread 8 August 2026
Photo

🎀 柚子:160/D/46/24歲 慵懶中帶點小性感 身材比例好,會穿搭,身上有淡淡的香氣 互動自然不冷場,屬於越玩放越開的類型 #雙北8000 ⭐茶客夏公告區😻 t.me/Line_tw226 𓆩點擊藍色字體看各地𓆪 [北部] [中部] [南部] ❦客評查看 t.me/kpinp 🦋🪽🪽🪽🧸🖤🦋🖤🦋 🌐LINE預約 tw226 🌐TG預約 @ttw226 ⭐Gleezy預約 tw226 🔅論壇: www.tw226.com

5 Aug 2026, 06:09 UTC31 viewsread 8 August 2026
Photo

🎀 莫凡:163/C+/46/28歲 看似溫柔屬性,實則到了床上放超開 主動激情舔食肉棒,主動掰穴等你插入 最愛在鏡前愛愛,看自己被幹的模樣更興奮 #新竹6000 ⭐茶客夏公告區😻 t.me/Line_tw226 𓆩點擊藍色字體看各地𓆪 [北部] [中部] [南部] ❦客評查看 t.me/kpinp 🦋🪽🪽🪽🧸🖤🦋🖤🦋 🌐LINE預約 tw226 🌐TG預約 @ttw226 ⭐Gleezy預約 tw226 🔅論壇: www.tw226.com

Showing the 12 most recent of 12 posts we hold for @bxx328. 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 5 registered channels — 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.

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 2 October 2026 — this entry's latest reading, not the date you are reading this.

“夏夏北部精選” (@bxx328), 255 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/bxx328.

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.