Telegram RegisterThe public register of Telegram
Telegram profile photo for 旅館推薦

Channel

旅館推薦

@av5251

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

2subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002500842092
TypeChannel
Username@av5251
Description好的皮囊千篇一律 有趣的靈萬裡挑一 希望大家可以給彼此一個機會~ 【服務時間13:00-03:00】
CreatedBetween 1 March 2025 and 15 May 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live20 August 2026
Measurements held2
On Telegramt.me/av5251

Growth

212 August 2026 — 2 subscribers14 August 2026 — 2 subscribers12 August 202614 August 2026
2 measurements spanning 2 days. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 02:022no change
12 Aug 2026, 01:012first reading

Engagement

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

What this channel posts

Photos
107

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

13 May 2026, 18:14 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

15 May 2025, 17:07 UTC109 viewsread 14 August 2026
Photo

#台北旅館 #萬華區 旅館名字:儷夏商旅 西門捷運館 旅館地址:台北市萬華區中華路一段90號 櫃檯電話:02 2311 6168 休息價位:880/2H

15 May 2025, 17:06 UTC104 viewsread 14 August 2026
Photo

#台中旅館 #烏日區 旅館名字:高鐵戀館 旅館地址:台中市烏日區新興路15號 休息價位:800/3H 電話:0423387808

15 May 2025, 17:06 UTC59 viewsread 14 August 2026
Photo

#新北旅館 #汐止區 旅館名字:慾望實境 旅館地址:新北市汐止區大同路一段118號 休息價位:980 / 2H 電話:0226419955

15 May 2025, 17:05 UTC49 viewsread 14 August 2026
Photo

#新北旅館 #土城區 旅館名字:艾曼 旅館地址:新北市土城區城林路6巷18號 休息價位:2H/1080 3H/1680 電話:0222673399

15 May 2025, 17:05 UTC33 viewsread 14 August 2026
Photo

#新竹旅館 #新竹市 旅館名字:琺何 旅館地址:新竹市東區振興路109號 電話:035610011 休息價位:3H/1480

15 May 2025, 17:05 UTC51 viewsread 14 August 2026
Photo

#新北旅館 #林口區 旅館名字:歐悅 旅館地址:新北市林口區文化三路二段115巷163號 櫃檯電話:0226086611 休息價位:3H/1000多

15 May 2025, 17:04 UTC25 viewsread 14 August 2026
Photo

#台北旅館 #中山區 旅館名字:大地清旅 旅館地址:台北市中山區長安東路二段246號 櫃檯電話:0227110102 休息價位:12H/1980

Showing the 8 most recent of 8 posts we hold for @av5251. 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

Citation-graph rank — 961,052 of 1,584,733entries 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.

Mentions

Named by 1 registered channel — 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.

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

“旅館推薦” (@av5251), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/av5251.

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.