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

Channel

Корпус 1.9 ДВФУ

@info_oss_1_9

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

20subscribers

-2 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-1003864658287
TypeChannel
Username@info_oss_1_9
CreatedBetween 1 February 2026 and 13 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 November 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/info_oss_1_9

Topic

Local community — 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 98% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@info_oss_1_9/36 · this entry13 Mar 2026, 07:53 UTC@info_oss_1_11/2513 Mar 2026, 07:53 UTC1.00under a minute
@info_oss_1_9/37 · this entry24 Mar 2026, 04:47 UTC@info_oss_1_11/2624 Mar 2026, 04:47 UTC1.00under a minute
@info_oss_1_9/38 · this entry14 Apr 2026, 03:00 UTC@info_oss_1_11/2714 Apr 2026, 03:00 UTC1.00under a minute
@info_oss_1_9/39 · this entry15 Apr 2026, 00:11 UTC@info_oss_1_11/2815 Apr 2026, 00:11 UTC1.00under a minute
@info_oss_1_9/50 · this entry1 Jun 2026, 00:00 UTC@info_oss_1_11/391 Jun 2026, 00:00 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
@info_oss_1_115 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (5–0)

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 0 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 16 comparable posts for this entry, running 13 March 2026 to 5 July 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 2 channels, the one whose matching posts we hold earliest is @info_oss_1_9 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key 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 2 registered channels linked by matching posts. 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

202321.57 August 2026 — 22 subscribers11 August 2026 — 22 subscribers15 October 2026 — 23 subscribers28 October 2026 — 22 subscribers4 November 2026 — 21 subscribers11 November 2026 — 20 subscribers7 August 202611 November 2026
6 measurements spanning 96 days, net -2. 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 20–23 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 07:4120-1
4 Nov 2026, 11:1121-1
28 Oct 2026, 21:3022-1
15 Oct 2026, 23:1623+1
11 Aug 2026, 12:4722no change
7 Aug 2026, 15:1722first reading

Engagement

20 posts held, back to 13 March 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 5 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

5 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩360.0%
🥰120.0%
🫡120.0%

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 3 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 5 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 13 March 2026 to 5 July 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

5 Jul 2026, 00:00 UTC11 viewsread 11 August 2026

Напоминаем, что завтра во всём корпусе будет проведена дезинсекция. Необходимо: Сложить все вещи в пакеты, чемоданы, коробки, всё переместить в центр комнаты Освободить кровать (подушку, одеяло, постельное белье и вещи из-под кровати упаковать в пакеты и убрать), а также поднять матрас Отключить от сети электроприборы, кроме холодильника По возможности отодвинуть холодильник от стены на 10-15 см Закрыть окно и …

1 Jul 2026, 03:30 UTC20 viewsread 11 August 2026

✅ Горячее водоснабжение восстановлено.

24 Jun 2026, 00:00 UTC28 viewsread 11 August 2026
Photo

Дезинсекция гостиничного корпуса 6 июля будет проведён третий этап мероприятий по обработке корпуса. А вы уже подписались на канал ДВФУ в национальном мессенджере? Пример подготовленных номеров к дезинсекции можно увидеть на фото. Во время проведения обработки и после неё в течение 4-5 часов нахождение в корпусе запрещено. В этот период можно провести время в административных и учебных корпусах.

19 Jun 2026, 06:56 UTC34 viewsread 11 August 2026

В связи с отключением горячего водоснабжения по причине реконструкции наружных тепловых сетей АО ДВЭУК в период с 19 июня по 01 июля 2026 года для проживающих в корпусах Малого Аякса организована возможность пользования душевыми с горячей водой. Доступ к душевым будет осуществляться в корпусе 6.2 ежедневно с 8:00 до 23:00 при предъявлении гостями пропуска о проживании на Малом Аяксе с внесением записи в журнал посет…

14 Jun 2026, 08:30 UTC37 viewsread 11 August 2026

Напоминаем, что завтра во всём корпусе будет проведена дезинсекция. Необходимо: 📎 Сложить все вещи в пакеты, чемоданы, коробки, всё переместить в центр комнаты 📎 Освободить кровать (подушку, одеяло, постельное белье и вещи из-под кровати упаковать в пакеты и убрать), а также поднять матрас 📎 Отключить от сети электроприборы, кроме холодильника 📎 По возможности отодвинуть холодильник от стены на 10-15 см 📎 Закрыть ок…

1 Jun 2026, 00:00 UTC40 viewsread 11 August 2026
Photo

Дезинсекция гостиничного корпуса 15 июня будет проведён второй этап мероприятий по обработке корпуса. А вы уже подписались на канал ДВФУ в национальном мессенджере? Пример подготовленных номеров к дезинсекции можно увидеть на фото. Во время проведения обработки и после неё в течение 4-5 часов нахождение в корпусе запрещено. В этот период можно провести время в административных и учебных корпусах.

26 May 2026, 03:23 UTC46 viewsread 11 August 2026
Photo

🌊 Заселение 2026 — что нужно знать? Рассказываем, как пройдёт заселение в гостиничные корпуса кампуса и городские общежития ДВФУ в 2026/2027 учебном году. 🗓️ Когда начнется заселение: • для первокурсников — с 09:00 14 сентября; • для студентов 2+ курсов — с 16 сентября; • заселение в городские общежития — с 09:00 7 сентября. ⚡️ Все подробности и информацию о документах, необходимых для заселения, читайте в нашей …

19 May 2026, 03:05 UTC45 views1 reactionsread 11 August 2026

✅ Горячее водоснабжение восстановлено.

🥰1

18 May 2026, 09:02 UTC46 views3 reactionsread 11 August 2026

В связи с продолжением ремонтно-восстановительных работ на сетях АО ДВЭУК «Генерация сети», восстановление горячего водоснабжения ожидается ориентировочно 19 мая.

💩3

17 May 2026, 07:32 UTC46 viewsread 11 August 2026

❗️Отключение горячего водоснабжения продлено до 18 мая.

17 May 2026, 00:00 UTC46 viewsread 11 August 2026

Напоминаем, что завтра во всём корпусе будет проведена дезинсекция. Необходимо: 📎 Сложить все вещи в пакеты, чемоданы, коробки, всё переместить в центр комнаты 📎 Освободить кровать (подушку, одеяло, постельное белье и вещи из-под кровати упаковать в пакеты и убрать), а также поднять матрас 📎 Отключить от сети электроприборы, кроме холодильника 📎 По возможности отодвинуть холодильник от стены на 10-15 см 📎 Закрыть ок…

7 May 2026, 02:35 UTC83 viewsread 11 August 2026

⚡️🚿 Временное отключение горячего водоснабжения Друзья, в период с 10 по 17 мая в связи с проведением АО ДВЭУК «Генерация сети» испытаний на прочность и плотность наружных тепловых сетей будет временно отключено горячее водоснабжение в следующих корпусах кампуса ДВФУ: Гостиничные корпуса: 1, 2, 3, 4, 5, 6.1, 6.2, 7.1, 7.2, 8.1, 8.2, 9, 10, 11 Учебные корпуса: A, B, C, D, E, F, G, L, S, S1, S2, стадион Корпуса м. А…

Showing the 12 most recent of 20 posts we hold for @info_oss_1_9. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Корпус 1.9 ДВФУ” (@info_oss_1_9), 20 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/info_oss_1_9.

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.