Photo, posted without a caption

Channel
LUPIN TRAVEL | CHANNEL
@lupintravel
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,114subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001100288839 |
|---|---|
| Type | Channel |
| Username | @lupintravel |
| Created | Between 1 December 2016 and 31 January 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/lupintravel |
Topic
Travel — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 07:38 | 1,114 | -1 |
| 9 Sept 2026, 02:15 | 1,115 | -2 |
| 3 Sept 2026, 18:18 | 1,117 | -1 |
| 31 Aug 2026, 01:27 | 1,118 | -2 |
| 27 Aug 2026, 22:25 | 1,120 | +1 |
| 24 Aug 2026, 19:54 | 1,119 | -1 |
| 20 Aug 2026, 21:33 | 1,120 | -1 |
| 17 Aug 2026, 13:15 | 1,121 | -1 |
| 11 Aug 2026, 01:15 | 1,122 | -3 |
| 8 Aug 2026, 00:01 | 1,125 | no change |
| 7 Aug 2026, 21:55 | 1,125 | first reading |
Engagement
20 posts held, back to 25 April 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
این تور لوکس تنها برای ۱۰ نفر برگزار میشود و با تکمیل ظرفیت، ثبتنام بسته خواهد شد. ☀️ این برنامه در تابستان امسال دیگر تکرار نخواهد شد. 📌 برای مشاهده جزئیات کامل خدمات و برنامه سفر، پست زیر را ببینید https://www.instagram.com/reel/Da-fWpDNl4x/?igsh=d25zODNtOHRud25n
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @lupintravel. 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.
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.
“LUPIN TRAVEL | CHANNEL” (@lupintravel), 1,114 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/lupintravel.
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.