Channel
@xlin55
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
306subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002031051956 |
|---|---|
| Type | Channel |
| Username | @xlin55 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/xlin55 |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 10 Oct 2026, 09:55 | 306 | -2 |
| 29 Sept 2026, 17:21 | 308 | +1 |
| 15 Sept 2026, 06:40 | 307 | +1 |
| 7 Sept 2026, 05:59 | 306 | -3 |
| 30 Aug 2026, 08:33 | 309 | -1 |
| 23 Aug 2026, 05:38 | 310 | +2 |
| 15 Aug 2026, 20:37 | 308 | -1 |
| 8 Aug 2026, 07:47 | 309 | no change |
| 7 Aug 2026, 13:08 | 309 | first reading |
7 posts held, back to 25 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 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 7 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
📍 #北部推薦 #雙北推薦 🇹🇼瑤怡 🔥🔥🔥 166/46/D/23歲 她能夠滿足你的任何幻想~ 跟她約會 是享受極致的誘惑和激情 😀 #12000一節 <#本照 #台妹 #外約> ➖➖➖🦋➖➖➖ 🔣📱 LINE➕ fu349 🔣✈️ 飛機➕@fnu99 🔣全台本照選妹區 🔣點擊加所以外約群組 🔣點我把TG變成中文版 ➖➖➖🦋➖➖➖ 😀 一律見面付現金 😀 不接受其他交易方式 不唬爛不騙人 長期經營 給我1次機會=給自己1次安心 外約交給我們給你最專業服務
📍 #北部推薦 #雙北推薦 🇹🇼小元 🔥🔥🔥 164/46/C/20歲 北一學生妹妹 身材苗條比例好 皮膚白嫩 五官精緻 第一次報班 乖巧聽話 😀 #10000一節 <#本照 #台妹 #外約> ➖➖➖🦋➖➖➖ 🔣📱 LINE➕ fu349 🔣✈️ 飛機➕@fnu99 🔣全台本照選妹區 🔣點擊加所以外約群組 🔣點我把TG變成中文版 ➖➖➖🦋➖➖➖ 😀 一律見面付現金 😀 不接受其他交易方式 不唬爛不騙人 長期經營 給我1次機會=給自己1次安心 外約交給我們給你最專業服務
📍 #北部推薦 #雙北推薦 🇹🇼只只 🔥🔥🔥 163/48/D+/23歲 百變甜心的感覺很甜美 水嫩肌膚隱約還透著淡紅粉 胸型漂亮 皮膚白 顏值很讚 😀 #6000一節 <#本照 #台妹 #外約> ➖➖➖🦋➖➖➖ 🔣📱 LINE➕ fu349 🔣✈️ 飛機➕@fnu99 🔣全台本照選妹區 🔣點擊加所以外約群組 🔣點我把TG變成中文版 ➖➖➖🦋➖➖➖ 😀 一律見面付現金 😀 不接受其他交易方式 不唬爛不騙人 長期經營 給我1次機會=給自己1次安心 外約交給我們給你最專業服務
📍 #北部推薦 #雙北推薦 🇹🇼十一 🔥🔥🔥 161/46/C+/23歲 學生妹短期報 #首次乾淨無套 外貌可愛 便宜大碗試車中 剛兼職服務不多 但會撒嬌態度好 #妙芙獨家報班資訊 😀 #6000一節 <#本照 #台妹 #外約> ➖➖➖🦋➖➖➖ 🔣📱 LINE➕ fu349 🔣✈️ 飛機➕@fnu99 🔣全台本照選妹區 🔣點擊加所以外約群組 🔣點我把TG變成中文版 ➖➖➖🦋➖➖➖ 😀 一律見面付現金 😀 不接受其他交易方式 不唬爛不騙人 長期經營 給我1次機會=給自己1次安心 外約交給我們給你最專業服務
我必須每天宣傳，因為這是我的工作，關於能不能成功一看勤奮，二看緣分，勤奮我做到了，緣分看你了！
📍 #北部推薦 #雙北推薦 🇹🇼雪雪 🔥🔥🔥 170/50/E+/24Y 精緻的臉蛋 讓人心生憐愛 #身材超讚 完美戀人般氛圍 😀 #27000一節 <#本照 #台妹 #外約> ➖➖➖🦋➖➖➖ 🔣📱 LINE➕ fu349 🔣✈️ 飛機➕@fnu99 🔣全台本照選妹區 🔣點擊加所以外約群組 🔣點我把TG變成中文版 ➖➖➖🦋➖➖➖ 😀 一律見面付現金 😀 不接受其他交易方式 不唬爛不騙人 長期經營 給我1次機會=給自己1次安心 外約交給我們給你最專業服務
📍 #北部推薦 #雙北推薦 🇹🇼舒瑤 🔥🔥🔥 168/46/D+/23Y 反差萌可愛清純型 高顔值 奶大 腰細 屁股翹 床上超級會扭 😀 #20000一節 <#本照 #台妹 #外約> ➖➖➖🦋➖➖➖ 🔣📱 LINE➕ fu349 🔣✈️ 飛機➕@fnu99 🔣全台本照選妹區 🔣點擊加所以外約群組 🔣點我把TG變成中文版 ➖➖➖🦋➖➖➖ 😀 一律見面付現金 😀 不接受其他交易方式 不唬爛不騙人 長期經營 給我1次機會=給自己1次安心 外約交給我們給你最專業服務
Showing the 7 most recent of 7 posts we hold for @xlin55. 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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“北部外約⚜️𝖑𝖎𝖓𝖊：𝐟𝐮𝟑𝟒𝟗” (@xlin55), 306 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/xlin55.
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.