Channel
@hotelarchives
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
24subscribers
+8 since we began measuring on 9 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004420291585 |
|---|---|
| Type | Channel |
| Username | @hotelarchives |
| Created | Between 1 June 2026 and 13 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/hotelarchives |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Nov 2026, 16:26 | 24 | +1 |
| 24 Oct 2026, 15:37 | 23 | +8 |
| 18 Oct 2026, 01:47 | 15 | -2 |
| 10 Oct 2026, 11:39 | 17 | +2 |
| 1 Oct 2026, 00:55 | 15 | -1 |
| 13 Sept 2026, 16:23 | 16 | no change |
| 9 Sept 2026, 16:47 | 16 | first reading |
20 posts held, back to 13 September 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 13 September 2026. An engagement rate over an empty window would be a number about nothing.
40 % خب، برای اینجا باید بگم که موضوع قشنگی داره. نحوه ی پست گذاریش قطعا نحوه ی خاص خودشو داره و خب کسی مثل من مخاطبش نمیشه پس باید ادم درست پیدا بشه، پیشنهاد میدم مرتب بشه پست گذاری و کاربردی تر باشن درصد بالا تر میره
50 % وایبش میتونه مخاطب رو مشتاق نگه داره اما اگه پست گذاشته نشه قطعا مخاطب لفت میده و ول میکنه
60 % جواب اینجا هم مثل این مورده.
65 % پتانسیل نسبتا بهتری داره، سبک محتوا کامل سلف کر نیست و همزمان هست، متفاوته و متوجهم، اگه بتونی یه مقدار وایب خاص و متفاوت توی چنل ایجاد کنی بهتر هم میشه
90 % موضوع هر پست متفاوت و قشنگه، و نحوه ی پست گذاری مرتبه
70 % جواب اینجا هم مثل این مورده.
70 % از اونجایی که چنل تازه پست گذاری میکنه نمیتونم زیاد نظری بدم، اما قطعا پتانسیل خوبی داره بخاطر کپشن پست ها و وایب خوبش
90 % خیلی خیلی موضوع جالبی رو در نظر گرفتی و پست های بامزه ای داری
80 % پرونده جنایی با کیفیت بالا میذاری چی از این بهتر؟
@xtris و @vteor بخاطر کیفیت پک های خیلی خوب و بالا ، کپشن های قشنگ و مخصوصا اسم خوبش تا 90 % رو میره
90 % موضوع جذاب، نحوه ی پست گذاری متفاوت و قشنگ، خود پست ها هم پتانسیل زیادی برای جذب ممبر دارن، فقط ادمای درست باید اینجا رو پیدا کنن 🙏
60 % پیشرفت اینجا فقط به یه چیز بستگی داره اونم پیدا کردن مخاطب خوب و موندگاره و یه پاکسازی اساسی توی چنل
Showing the 12 most recent of 20 posts we hold for @hotelarchives. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
@hotelarchives named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“ ᒪITTᒪᗴ ᕼOᑌՏᗴ” (@hotelarchives), 24 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/hotelarchives.
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.