Telegram RegisterThe public register of Telegram
Telegram profile photo for Бирюлёво Восточное

Channel

Бирюлёво Восточное

@Birulovo_Vostochnoe

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

4,521subscribers

+3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001772701661
TypeChannel
Username@Birulovo_Vostochnoe
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/Birulovo_Vostochnoe

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
@Birulovo_Vostochnoe/11095 · this entry3 Aug 2026, 11:50 UTC@Vostocnoe_Raion/49983 Aug 2026, 11:52 UTC1.002 minutes
@Birulovo_Vostochnoe/11097 · this entry3 Aug 2026, 12:56 UTC@Vostocnoe_Raion/50003 Aug 2026, 12:56 UTC1.00under a minute
@Birulovo_Vostochnoe/11111 · this entry5 Aug 2026, 13:47 UTC@Vostocnoe_Raion/50035 Aug 2026, 13:47 UTC1.00under a minute
@Birulovo_Vostochnoe/11120 · this entry7 Aug 2026, 06:54 UTC@Vostocnoe_Raion/50127 Aug 2026, 06:54 UTC1.00under a minute
@Birulovo_Vostochnoe/11121 · this entry7 Aug 2026, 06:54 UTC@Vostocnoe_Raion/50147 Aug 2026, 06:54 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
@Vostocnoe_Raion5 (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 11 comparable posts for this entry, running 3 August 2026 to 12 August 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 @Birulovo_Vostochnoe — 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

4,5044,5234,513.57 August 2026 — 4,518 subscribers7 August 2026 — 4,518 subscribers8 August 2026 — 4,519 subscribers10 August 2026 — 4,518 subscribers14 August 2026 — 4,517 subscribers17 August 2026 — 4,518 subscribers20 August 2026 — 4,523 subscribers24 August 2026 — 4,520 subscribers30 August 2026 — 4,522 subscribers1 September 2026 — 4,520 subscribers6 September 2026 — 4,516 subscribers11 September 2026 — 4,515 subscribers10 October 2026 — 4,512 subscribers14 October 2026 — 4,505 subscribers17 October 2026 — 4,506 subscribers21 October 2026 — 4,508 subscribers23 October 2026 — 4,504 subscribers26 October 2026 — 4,505 subscribers30 October 2026 — 4,507 subscribers1 November 2026 — 4,515 subscribers4 November 2026 — 4,509 subscribers8 November 2026 — 4,516 subscribers16 November 2026 — 4,521 subscribers4,5217 August 202616 November 2026
23 measurements spanning 102 days, net +3. 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 4,501–4,526 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
16 Nov 2026, 21:594,521+5
8 Nov 2026, 02:094,516+7
4 Nov 2026, 19:074,509-6
1 Nov 2026, 16:104,515+8
30 Oct 2026, 02:114,507+2
26 Oct 2026, 20:564,505+1
23 Oct 2026, 20:494,504-4
21 Oct 2026, 05:314,508+2
17 Oct 2026, 18:004,506+1
14 Oct 2026, 12:044,505-7
10 Oct 2026, 23:364,512-3
11 Sept 2026, 08:384,515-1
6 Sept 2026, 18:384,516-4
1 Sept 2026, 22:074,520-2
30 Aug 2026, 01:544,522+2
24 Aug 2026, 09:174,520-3
20 Aug 2026, 07:024,523+5
17 Aug 2026, 14:344,518+1
14 Aug 2026, 01:164,517-1
10 Aug 2026, 23:114,518first reading

Engagement

21 posts held, back to 3 August 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 7 pages 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 21 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 16s
Average length
23s

Measured directly from 6 videos 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

58 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 48.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬2848.3%
👍1220.7%
❤1119.0%
🥱35.17%
🌚23.45%
👌11.72%
😁11.72%

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

Measured over the 21 most recent posts we hold, published 3 August 2026 to 12 August 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

12 Aug 2026, 06:54 UTC121 views1 reactionsread 12 August 2026
Photo

‍ Шикарный асфальт на Липецкой, 40 | #ЮАО, #мoс #Тг #мcк

😁1

12 Aug 2026, 06:54 UTC118 viewsread 12 August 2026
Photo

Бирюлево Западное 1993 год Доброе утро! Бирюлево, Царицыно #Тг #мcк

12 Aug 2026, 06:53 UTC121 views1 reactionsread 12 August 2026
Photo

На Касимовской, 33 строят дом по реновации. В нём будет 208 квартир с потолками 2,65 метра. Сделают большие окна, остеклённые балконы и лоджии, а также корзины под кондиционеры. Подъезды планируют просторными, со сквозным проходом, помещением для консьержа, витражным остеклением и колясочной. Внешний вид дома и его расположение на карте — в прикреплённом фото. Заселение намечено на 2027 год. #ЮАО, #мoс #Тг #мc…

❤1

12 Aug 2026, 06:52 UTC120 viewsread 12 August 2026
Photo

Бирюлёво Западное, 1993 год. Бирюлево #Тг #мcк

8 Aug 2026, 21:27 UTC804 viewsread 12 August 2026
Photo

На станции «Липецкая» Бирюлевской линии активно строят объездную дорогу. Вот свежие кадры со стройплощадки. Бирюлево, Царицыно #Тг #мcк

8 Aug 2026, 21:27 UTC746 views0 reactionsread 12 August 2026
Video

На Липецкой улице без светофора. Люди на остановки бегут прямо под машины. На дублёре под окнами теперь полноценная трасса. Бирюлево #Тг #мcк

7 Aug 2026, 06:54 UTC957 views1 reactionsread 12 August 2026
Video

Вчера вечером был пожар на Булатниковском проезде, дом 14, к1 Причины пожара устанавливаются. Бирюлево, Царицыно #Тг #мcк

❤1

7 Aug 2026, 06:54 UTC892 views5 reactionsread 12 August 2026
Photo

‍‍‍‍‍‍ Кто помнит автобус номер 693?) Раньше он ходил от товарки через пасажирку, но только в будни и лишь с 10 до 16 часов!) Зато радует, что маршрут с809 почти такой же, жаль что он ходит лишь раз в час-полтора.. Доброе утро! Бирюлево, Царицыно #Тг #мcк

❤5

7 Aug 2026, 06:54 UTC874 views3 reactionsread 12 August 2026
Video

На камеру попал очаровательный обитатель столичного зоопарка —морской заяц МаКС #ЮАО, #мoс #Тг #мcк

❤3

7 Aug 2026, 06:54 UTC736 viewsread 12 August 2026
Photo

Шикарная луна над Братеево #ЮАО, #мoс #Тг #мcк

6 Aug 2026, 07:04 UTC597 viewsread 8 August 2026
Forwarded from @innoclusterPhoto

📢 В столице завершился отбор участников новой программы для российских инноваторов «Техлаб Москва» Она ориентирована на разработку и внедрение наукоемких решений на базе ИИ в разных сферах — от робототехники до новых материалов. В первом потоке конкурсантам нужно было подготовить варианты решения 10 технологических задач компаний-заказчиков. «За три месяца заявки подали больше 1,2 тысячи человек из 53 регионов Рос…

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Named by 2 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

БИРЮЛЁВО | ЦАРИЦЫНО ОНЛАЙН
@birulevo_tsar_online · 22,527
Telegram ranks this channel #3 of 28 here — alongside 27 others — read 21 September 2026
ЮАО ОНЛАЙН МОСКВА
@uao_online_msk · 64,905
Telegram ranks this channel #33 of 77 here — alongside 76 others — read 21 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Бирюлёво Восточное” (@Birulovo_Vostochnoe), 4,521 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Birulovo_Vostochnoe.

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.