Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇨🇦 Щоденник групової поїздки в Канаду

Channel

🇨🇦 Щоденник групової поїздки в Канаду

@ubc_tmu_23

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

26subscribers

-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-1001971879266
TypeChannel
Username@ubc_tmu_23
CreatedBetween 1 April 2023 and 23 July 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live20 November 2026
Measurements held3
Confirmed unchanged6 times, most recently 20 November 2026
On Telegramt.me/ubc_tmu_23

Topic

Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 16 October 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 the other topics.

Growth

262726.57 August 2026 — 27 subscribers11 August 2026 — 27 subscribers14 October 2026 — 26 subscribers7 August 202614 October 2026
3 measurements spanning 68 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 26–27 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 14:1826-1
11 Aug 2026, 07:0127no change
7 Aug 2026, 15:3027first reading

Engagement

20 posts held, back to 23 July 2023 — 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 28 July 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 03s
Average length
2m 03s

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

210 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10650.5%
👍6832.4%
🔥178.10%
😢83.81%
🤝52.38%
🥰52.38%
🎉10.476%

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 20 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 210 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 23 July 2023 to 28 July 2023, 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

28 Jul 2023, 09:38 UTC132 views14 reactionsread 11 August 2026

Це ще не все:) 📷 Зібрала всі наші фото та відео з поїздки на Google Drive. Подивитися та завантажити всі файли можна тут ➡️ https://drive.google.com/drive/folders/19TISgRlmRHwY13qOt-MSEPvjTkpjph5j?usp=drive_link 📝 Також прошу ваш заповнити коротку форму та залишити ваш відгук про поїздку в Канаду. Лише декілька хвилин вашого часу — це дуже важливо ❤️ Щоб заповнити форму, будь ласка, перейдіть за посиланням https:/…

❤6👍6🥰2

28 Jul 2023, 09:36 UTC133 views14 reactionsread 11 August 2026
Video

❤️ Всім привіт:) Ну що, от ми всі й повернулися з подорожі та роз'їхалися різними країнами та містами. Нарешті всі отримали свої валізи 😁 🇨🇦 Ділюся з вами нашим відеозвітом — на згадку про цю супернасичену, моментами складну, але дуууже цікаву подорож, яка дозволила нам побачити та порівняти два найпопулярніших канадських міста 😌

❤12🔥1🥰1

26 Jul 2023, 03:52 UTC83 views7 reactionsread 11 August 2026

Всім доброго ранку) 🕗 Виїжджаємо у Київ о 08:00. Протягом дня писатиму, де ми й як) ❤️ Зустрічаємося ввечері в ЖК Новопечерські Липки 🙌🏻

❤7

25 Jul 2023, 11:45 UTC83 views6 reactionsread 11 August 2026

Заселилися в готель) Пізніше напишу, коли будемо виїжджати завтра вранці в Київ)

👍5❤1

25 Jul 2023, 10:33 UTC72 views14 reactionsread 11 August 2026

Все пройшли, вже в Україні 🇺🇦❤️

👍9❤4🎉1

25 Jul 2023, 09:51 UTC73 views11 reactionsread 11 August 2026

Приїхали на польський кордон, на Краківець, тут жодного автобуса, тож сподіваюся, що пройдемо все швидко)

👍8❤3

25 Jul 2023, 05:59 UTC73 views10 reactionsread 11 August 2026

Добрий ранок! Виїжджаємо у Львів сьогодні вже о 08:30. Напишу, коли будемо на кордоні та як пройдемо його 🙌🏻

❤9👍1

24 Jul 2023, 19:09 UTC71 views13 reactionsread 11 August 2026

Завтра вранці виїжджаємо у Львів, про час виїзду повідомлю окремо. Ночуємо у Львові. 26 липня (середа) виїжджаємо у Київ та приїжджаємо ввечері на Новопечерські Липки. ❤️ тепер підемо відпочивати (ура) 🎊

❤8👍5

24 Jul 2023, 19:07 UTC70 views13 reactionsread 11 August 2026

Забрали валізи 🫡❤️

👍8🔥3❤2

24 Jul 2023, 17:18 UTC70 views11 reactionsread 11 August 2026
Photo

Рейс із Франкфурта затримується, підемо шукати багаж о 20:30) це тут поруч із готелем 🙌🏻 Одразу надам актуальну інформацію

👍8❤3

24 Jul 2023, 13:44 UTC67 views9 reactionsread 11 August 2026

Заселилися в готель Hilton біля аеропорту, про валізи конкретну інформацію знатиму після 19:00 🙌🏻

❤8👍1

Showing the 12 most recent of 20 posts we hold for @ubc_tmu_23. 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 14 October 2026 — this entry's latest reading, not the date you are reading this.

“🇨🇦 Щоденник групової поїздки в Канаду” (@ubc_tmu_23), 26 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/ubc_tmu_23.

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.