Telegram RegisterThe public register of Telegram
Telegram profile photo for Переселенцы на Дальний Восток

Channel

Переселенцы на Дальний Восток

@pereseleniedv

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

698subscribers

+7 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-1002085677904
TypeChannel
Username@pereseleniedv
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/pereseleniedv

Topic

Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Growth

689698693.57 August 2026 — 691 subscribers8 August 2026 — 691 subscribers14 August 2026 — 689 subscribers22 August 2026 — 690 subscribers29 August 2026 — 695 subscribers13 September 2026 — 698 subscribers7 August 202613 September 2026
6 measurements spanning 37 days, net +7. 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 688–699 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 21:41698+3
29 Aug 2026, 19:07695+5
22 Aug 2026, 16:03690+1
14 Aug 2026, 21:54689-2
8 Aug 2026, 02:20691no change
7 Aug 2026, 15:22691first reading

Engagement

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

Reaction mix

77 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 48.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3748.1%
👍3444.2%
💩33.90%
22.60%
🔥11.30%

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 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 77 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 11 March 2026 to 22 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

22 Jul 2026, 11:24 UTC229 views5 reactionsread 8 August 2026

Почему фамилия семьи могла измениться при переселении https://dzen.ru/a/amCnZBZOjlQebXKv

5

9 Jul 2026, 08:46 UTC433 views3 reactionsread 8 August 2026

Списки переселенцев в Приморский край 1903-1930 гг. (часть 11) https://dzen.ru/a/ak9fTuKJCirWAFP7

👍3

30 Jun 2026, 08:12 UTC550 views3 reactionsread 8 August 2026

Смена сословия при переселении или почему казаки становились крестьянами https://dzen.ru/a/akN5mp8RGgSdNoaF

👍3

25 Jun 2026, 07:50 UTC638 views1 reactionsread 8 August 2026

Как найти женщину-переселенку https://dzen.ru/a/ajzdTwB9WS1V9YTk

👍1

19 Jun 2026, 10:41 UTC645 views5 reactionsread 8 August 2026

Список переселенцев в Приморский край в 1900-1929 гг (часть 10) https://dzen.ru/a/ajT8Nl6_NRnsm9xY

👍32

16 Jun 2026, 12:39 UTC559 views3 reactionsread 8 August 2026

Список переселенцев в Приморский край в 1892 году https://dzen.ru/a/ajFDoHzHDzmdMMdA

👍3

2 Jun 2026, 08:59 UTC691 views6 reactionsread 8 August 2026

Список переселенцев в Приморский край в 1893 году https://dzen.ru/a/ah6aY53EfVGYwQQ6

👍51

28 May 2026, 10:37 UTC729 views2 reactionsread 8 August 2026

Почему в документах может отсутствовать часть семьи https://dzen.ru/a/ahgabGLs-THZQiDb

👍2

22 May 2026, 10:07 UTC762 views6 reactionsread 8 August 2026

Список переселенцев в Приморский край в 1907-1929 гг (часть 8) https://dzen.ru/a/ag2VCyTR_mCBftjm

41🔥1

3 May 2026, 13:30 UTC804 views4 reactionsread 8 August 2026

Как фиксировались дети в переселенческих документах https://dzen.ru/a/afdNedsi4zPELdkD

4

2 May 2026, 12:02 UTC649 views1 reactionsread 8 August 2026

Список переселенцев в Южно-Уссурийский (Приморский) край 1907-1915 гг (часть 7) https://dzen.ru/a/afXnLEsk-zqFHYKd

👍1

25 Apr 2026, 10:39 UTC723 views6 reactionsread 8 August 2026

Промежуточные пункты и временные поселения https://dzen.ru/a/aeyZbB5RWVEyWfXv

👍42

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

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.

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

“Переселенцы на Дальний Восток” (@pereseleniedv), 698 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/pereseleniedv.

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.