Telegram RegisterThe public register of Telegram

Channel

10 Корпус ДВФУ

@dvfu_10

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

929subscribers

+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-1001434356471
TypeChannel
Username@dvfu_10
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/dvfu_10

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 73% 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.

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 word for word on 3 other registered channels. 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/1402 · this entry15 Dec 2025, 06:31 UTC@dvfu_7_2/129915 Dec 2025, 06:34 UTC1.002 minutes
@dvfu_7_2/130121 Dec 2025, 02:02 UTC@dvfu_10/1404 · this entry21 Dec 2025, 02:04 UTC1.0072 seconds
@dvfu_11/135315 Dec 2025, 06:31 UTC@dvfu_10/1402 · this entry15 Dec 2025, 06:31 UTC1.00under a minute
@dvfu_11/135521 Dec 2025, 02:02 UTC@dvfu_10/1404 · this entry21 Dec 2025, 02:04 UTC1.002 minutes
@dvfu_10/1405 · this entry22 Dec 2025, 00:28 UTC@dvfu_11/135622 Dec 2025, 00:28 UTC1.00under a minute
@fefu_materik/84521 Dec 2025, 02:02 UTC@dvfu_10/1404 · this entry21 Dec 2025, 02:04 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@dvfu_7_214 (8/8 hand-verifiable sample passed)1.00under a minute@dvfu_7_2 (113)
@dvfu_1112 (8/8 hand-verifiable sample passed)1.00under a minute@dvfu_11 (102)
@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 9 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 30 October 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).

Across the whole group of 4, the earliest publisher we hold is @dvfu_10 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

928929928.57 Aug 2026, 16:47 — 928 subscribers8 Aug 2026, 00:51 — 928 subscribers8 Aug 2026, 02:21 — 929 subscribers7 Aug 2026, 16:478 Aug 2026, 02:21
3 measurements taken within a single day, 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 928–929 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 02:21929+1
8 Aug 2026, 00:51928no change
7 Aug 2026, 16:47928first reading

Engagement

19 posts held, back to 30 October 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 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

188 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 55.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10555.9%
👎4624.5%
❤‍🔥105.32%
🔥105.32%
😢63.19%
💯52.66%
👍31.60%
🥰21.06%
👏10.532%

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 19 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 188reactions 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 30 October 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:02 UTC688 views29 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

👎29

23 Jan 2026, 08:04 UTC≈1,430 views0 reactionsread 8 August 2026
Forwarded from @aykaidanovichPhoto

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

10 Jan 2026, 05:23 UTC≈1,240 views13 reactionsread 8 August 2026
Forwarded from @fefudvfu

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

8👎5

30 Dec 2025, 04:01 UTC≈1,490 views7 reactionsread 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 до

7

29 Dec 2025, 07:35 UTC931 views3 reactionsread 8 August 2026
Video

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

3

29 Dec 2025, 02:07 UTC773 views5 reactionsread 8 August 2026
Forwarded from @fefudvfuPhoto

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

5

25 Dec 2025, 01:51 UTC744 views11 reactionsread 8 August 2026
Forwarded from @aykaidanovichPhoto

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

5❤‍🔥4🥰2

22 Dec 2025, 00:28 UTC≈1,130 views10 reactionsread 8 August 2026

🎄Изменение режима работы бельевой В период новогодних праздников бельевая будет работать по следующему расписанию: С 31 декабря 2025 года по 5 января 2026 года и с 7 по 11 января 2026 года бельевая не работает. Единственный рабочий день – 6 января 2026 года: 12:00 - 13:00 и 17:00 - 18:00.

10

21 Dec 2025, 02:04 UTC≈1,170 views9 reactionsread 8 August 2026
Photo

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

9

18 Dec 2025, 02:03 UTC≈1,230 views6 reactionsread 8 August 2026
Photo

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

6

15 Dec 2025, 06:31 UTC≈1,080 views17 reactionsread 8 August 2026

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

12💯5

10 Dec 2025, 08:01 UTC≈1,320 views14 reactionsread 8 August 2026

В рамках программы капитального ремонта и оснащения 800 общежитий в период 2025 – 2030 гг. могут быть включены гостиничные корпуса №9 и №10. Приглашаем всех желающих принять участие в коротком опросе по ссылке☀️ Опрос будет доступен до 12 декабря 2025 года. Ваше мнение важно!👀

8😢6

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

“10 Корпус ДВФУ” (@dvfu_10), 929 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/dvfu_10.

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.