Telegram RegisterThe public register of Telegram
Telegram profile photo for 2.5 Корпус ДВФУ

Channel

2.5 Корпус ДВФУ

@dvfu_2_5

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

304subscribers

-13 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-1001216686771
TypeChannel
Username@dvfu_2_5
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/dvfu_2_5

Topic

Local community — 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 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@dvfu_10/140215 Dec 2025, 06:31 UTC@dvfu_2_5/1344 · this entry15 Dec 2025, 06:32 UTC1.0072 seconds
@dvfu_10/140421 Dec 2025, 02:04 UTC@dvfu_2_5/1346 · this entry21 Dec 2025, 02:04 UTC1.00under a minute
@dvfu_10/140829 Dec 2025, 07:35 UTC@dvfu_2_5/1349 · this entry29 Dec 2025, 07:35 UTC1.00under a minute
@dvfu_2_5/1344 · this entry15 Dec 2025, 06:32 UTC@dvfu_7_2/129915 Dec 2025, 06:34 UTC1.0072 seconds
@dvfu_7_2/130121 Dec 2025, 02:02 UTC@dvfu_2_5/1346 · this entry21 Dec 2025, 02:04 UTC1.0072 seconds
@dvfu_7_2/130429 Dec 2025, 07:35 UTC@dvfu_2_5/1349 · this entry29 Dec 2025, 07:35 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@dvfu_1012 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–4)
@dvfu_7_212 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–2)
@dvfu_1111 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–2)
@fefu_materik6 (6/6 hand-verifiable sample passed)1.00under a minuteeven

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 10 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 10 November 2025 to 25 February 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 5 channels, the one whose matching posts we hold earliest is @dvfu_10. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

304319311.57 August 2026 — 317 subscribers8 August 2026 — 317 subscribers24 August 2026 — 319 subscribers30 August 2026 — 317 subscribers8 September 2026 — 315 subscribers15 September 2026 — 314 subscribers30 September 2026 — 309 subscribers11 October 2026 — 308 subscribers26 October 2026 — 306 subscribers3 November 2026 — 305 subscribers9 November 2026 — 304 subscribers7 August 20269 November 2026
11 measurements spanning 94 days, net -13. 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 302–321 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Nov 2026, 22:55304-1
3 Nov 2026, 05:07305-1
26 Oct 2026, 19:49306-2
11 Oct 2026, 09:42308-1
30 Sept 2026, 06:36309-5
15 Sept 2026, 16:38314-1
8 Sept 2026, 17:56315-2
30 Aug 2026, 03:36317-2
24 Aug 2026, 01:53319+2
8 Aug 2026, 07:33317no change
7 Aug 2026, 16:04317first reading

Engagement

19 posts held, back to 10 November 2025 — 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 19 posts for this entry, the most recent from 25 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

35 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 37.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎1337.1%
😢1131.4%
👍411.4%
❤25.71%
🔥25.71%
🥰25.71%
😁12.86%

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

Measured over the 19 most recent posts we hold, published 10 November 2025 to 25 February 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

25 Feb 2026, 02:03 UTC174 views2 reactionsread 8 August 2026
Photo

❗️Каналы корпусов переехали Вся оперативная информация для проживающих публикуется только в каналах в МАХ. Ищите ваш корпус и подписывайтесь, чтобы не пропустить важные новости! 📍 Малый Аякс: • корпус 1.8 • корпус 1.9 • корпус 1.10 • корпус 1.11 • корпус 2.1 • корпус 2.2 • корпус 2.3 • корпус 2.4 • корпус 2.5 • корпус 2.6 • корпус 2.7 📍 Северные: • корпус 6.1 • корпус 6.2 • корпус 7.1 • корпус 7.2 • корпус 8.1 …

👎2

23 Jan 2026, 08:01 UTC401 views3 reactionsread 8 August 2026
Forwarded from @aykaidanovichPhoto

🎓 День студента — это больше, чем просто день Это люди, идеи, движение и энергия, которые живут в университете каждый день. 📨 26–30 января Почтовая станция с уникальными открытками для родных и близких Корпус А, уровень 6 | 10:00–18:00 📅 25 января 🌠 Служба ко Дню памяти Святой мученицы Татьяны ул. Пушкинская, 29Б, Татьянинский храм | 10:00 ⚡️ «Квиз, плиз!» — интеллектуальная битва Корпус А, уровень 12 | 16:00 📅 …

👍1🔥1🥰1

23 Jan 2026, 06:43 UTC309 viewsread 8 August 2026
Photo

Отключение воды🚰 Частично в корпусе в связи с внеплановыми ремонтными работами будет отсутствовать горячее и холодное водоснабжение. Дата: сегодня, 23 января Время: до 19:00 (ориентировочно) Приносим извинения за доставленные неудобства🩵

10 Jan 2026, 05:23 UTC332 views1 reactionsread 8 August 2026
Forwarded from @fefudvfu

🚌 На время непогоды движение шаттлов приостанавливается Чтобы обеспечить безопасность движения и беспрепятственную уборку дорог в кампусе, движение внутрикампусных шаттлов временно приостановлено. 🚐 Городские шаттлы в текущее время работают в штатном режиме.

😢1

4 Jan 2026, 23:10 UTC413 views5 reactionsread 8 August 2026
Photo

Отключение горячей воды🚰 Частично в корпусе в связи с внеплановыми ремонтными работами будет отсутствовать горячее водоснабжение. Дата: сегодня, 5 января Время: до 18:00 (ориентировочно) Приносим извинения за доставленные неудобства🩵

👎5

30 Dec 2025, 04:01 UTC337 viewsread 8 August 2026
Forwarded from @ekc_dvfuPhoto

⚡️Как будет работать инфраструктура кампуса в новогодние праздники? Собрали в одном месте расписание работы ключевых точек кампуса в новогодние праздники — сохраняйте пост и делитесь с друзьями! 🍔 Точки питания: Столовая, корпус 3: 31 декабря – с 08.00 до 17.30 1 января – выходной со 2 января – с 08.00 до 20.00 Столовая, корпус 10: 31 декабря – с 08.30 до 17.30 1 января – с 10.00 до 19.00 со 2 января – с 08.30 до…

29 Dec 2025, 07:35 UTC183 viewsread 8 August 2026
Video

🗂Приём студентов и сотрудников по вопросам проживания в Студенческом офисе (3-е окно) завтра, 30 декабря, осуществляется до 13:00. P.S. Свой вопрос вы также можете задать в чате ДГиС или направить через сервис «Единое окно» в личном кабинете 📬

29 Dec 2025, 02:07 UTC230 views3 reactionsread 8 August 2026
Forwarded from @fefudvfuPhoto

🚌🎄 Как будут работать шаттлы в новогодние праздники Друзья, в период новогодних каникул движение автобусов ДВФУ будет временно изменено. ❄️ Городские шаттлы С 31 декабря по 8 января включительно городские шаттлы ДВФУ не работают. ❄️ Маршрут «Малый Аякс — Корпус А» С 31 декабря по 11 января включительно автобус на маршруте «Малый Аякс — Корпус А» не работает. ❄️ Шаттлы в кампусе Основные внутрикампусные шаттлы …

😢2👍1

25 Dec 2025, 01:51 UTC229 views3 reactionsread 8 August 2026
Forwarded from @aykaidanovichPhoto

Новый год — про встречи с теми, кто рядом 🎄В ДВФУ в новогоднюю ночь и на Рождество будет действовать круглосуточный гостевой режим. 🕖 Круглосуточный доступ гостей внутри жилых корпусов и между ними (в кампусе и на материке) будет доступен для студентов и сотрудников ДВФУ с действующим персональным пропуском: 🌲 с 31 декабря по 1 января — без ограничения по времени пребывания; 🌲 с 6 января по 7 января — без ограничен…

👍1🔥1😁1

21 Dec 2025, 02:04 UTC295 views3 reactionsread 8 August 2026
Photo

Пришла бронь на переселение / заселение, но вы уже уехали встречать Новый год домой?🎄 Для студентов, чьи брони на переселение / заселение действительны с 25 декабря, срок действия броней будет автоматически продлён до 12 января включительно 🔥Данная возможность действительна только в период новогодних каникул Дополнительно подавать обращения не нужно

❤1👍1🥰1

18 Dec 2025, 02:03 UTC330 views0 reactionsread 8 August 2026
Photo

Основные рекомендации по пожарной безопасности С приближением длительных праздничных дней рекомендуем выполнить несколько простых действий для обеспечения безопасных условий: 🔥Перед тем как покинуть комнату, обязательно выключите все источники света, отключите электроприборы от сети и отсоедините удлинители. 🔥Если планируете уехать на срок более 1 дня, заранее сообщите администратору посредством личного уведомлени…

15 Dec 2025, 06:32 UTC281 viewsread 8 August 2026

Если вы планируете уехать на новогодние каникулы, рекомендуем подготовить комнату. Подготовили для вас самые важные пункты: 1️⃣Убрать скоропортящиеся продукты 2️⃣Выключить свет и электроприборы 3️⃣Убедиться, что окно закрыто 4️⃣Вынести мусор 5️⃣Закрыть дверь на ключ Также рекомендуем заранее оплатить размещение за январь. В связи с длительными выходными и обработкой платежей в течение 3 рабочих дней у вас может обр…

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

“2.5 Корпус ДВФУ” (@dvfu_2_5), 304 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/dvfu_2_5.

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.