Telegram RegisterThe public register of Telegram
Telegram profile photo for 小富婆旅馆(日租1100🐷)

Channel

小富婆旅馆(日租1100🐷)

@xiaofupojiejie1122

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

343subscribers

+1 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-1001730488039
TypeChannel
Username@xiaofupojiejie1122
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/xiaofupojiejie1122

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

340347343.57 August 2026 — 342 subscribers8 August 2026 — 342 subscribers15 August 2026 — 345 subscribers21 August 2026 — 347 subscribers28 August 2026 — 343 subscribers6 September 2026 — 340 subscribers13 September 2026 — 343 subscribers3437 August 202613 September 2026
7 measurements spanning 37 days, net +1. 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 339–348 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 19:21343+3
6 Sept 2026, 21:57340-3
28 Aug 2026, 22:56343-4
21 Aug 2026, 09:27347+2
15 Aug 2026, 00:59345+3
8 Aug 2026, 07:01342no change
7 Aug 2026, 11:07342first reading

Engagement

20 posts held, back to 6 February 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 20 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3s
Average length
3s

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.

Reaction mix

27 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1866.7%
👌27.41%
👍27.41%
😢27.41%
😱27.41%
🥱13.70%

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 10 of the 20 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 February 2026 to 17 July 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.

Recent posts

15 Apr 2026, 04:30 UTC≈4,800 views0 reactionsread 8 August 2026

房间 包月!包月!包月! 房间 包月!包月!包月! 一个月 10000 包水不包电,电费按照电力局的收费来算,目前45🐷一度, 24小时星联WiFi,空调24小时可用 有热水,有保姆打扫,押金有3000🐷 @xiaofupojie

6 Apr 2026, 08:55 UTC≈4,090 views2 reactionsread 8 August 2026

大量需要开发,底薪1.2w,在村外,出入自由,需要的宝宝,可以滴滴店主哦

👍2

4 Apr 2026, 12:35 UTC≈3,860 views7 reactionsread 8 August 2026
Video

月租的宝宝们,本月开始电费都是48🐷一度了噶,店主没有多要一株哈,电力局多少,咱就收多少。店主决定今天开始用风扇了🤣🤣

👌2😢2😱2🥱1

4 Apr 2026, 12:32 UTC≈3,450 views2 reactionsread 8 August 2026
Forwarded from @yatai1368Photo

#水沟谷电力局通知📢:电费价格将进行调整。 此前,电费按每单位 35 泰铢收取。由于当前形势,现调整为新价格如下: • 家庭用电(单相电表):每单位 45 泰铢 • 商业用电(三相电表):每单位 48 泰铢 新的电价标准自本月起开始执行。 鉴于电价已作调整,为避免产生不必要的电费开支,提醒大家按需用电,节约使用。 对于可能带来的不便,敬请谅解。

❤2

3 Apr 2026, 10:19 UTC≈3,020 viewsread 8 August 2026

月租费空一间,需要的宝宝,滴滴 @xiaofupojie

28 Mar 2026, 09:24 UTC≈3,150 viewsread 8 August 2026

月租目前有一间,需要的抓紧滴滴哦 @xiaofupojie

28 Mar 2026, 09:23 UTC≈3,150 views1 reactionsread 8 August 2026

房间 包月!包月!包月! 房间 包月!包月!包月! 一个月 10000 包水不包电,电费按照电力局的收费来算,目前45🐷一度, 24小时星联WiFi,空调24小时可用 有热水,有保姆打扫,押金有3000🐷

❤1

27 Mar 2026, 12:10 UTC≈3,010 views1 reactionsread 8 August 2026

‼️公司大量招 ,老手工资1.2 w,出入自由,想了解的宝宝滴滴 @huashengmi011

❤1

25 Mar 2026, 04:05 UTC≈2,980 viewsread 8 August 2026

家人们,最近亚太这边好多失业的人,到处都有小偷,出去或者睡觉的时候,大家记得把窗门都锁好,贵重物品都藏好‼️

23 Mar 2026, 08:29 UTC≈2,910 viewsread 8 August 2026

今日日租有一间哦,需要的滴滴富婆姐姐 @xiaofupojie

Showing the 12 most recent of 20 posts we hold for @xiaofupojiejie1122. 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

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

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

“小富婆旅馆(日租1100🐷)” (@xiaofupojiejie1122), 343 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/xiaofupojiejie1122.

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.