Telegram RegisterThe public register of Telegram
Telegram profile photo for Летопись Лютого Зверя

Channel

Летопись Лютого Зверя

@berggphoto

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

298subscribers

+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-1001979677673
TypeChannel
Username@berggphoto
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/berggphoto

Growth

297298297.57 August 2026 — 297 subscribers8 August 2026 — 297 subscribers15 September 2026 — 298 subscribers7 August 202615 September 2026
3 measurements spanning 39 days, 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 297–298 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 11:39298+1
8 Aug 2026, 08:04297no change
7 Aug 2026, 14:55297first reading

Engagement

6 posts held, back to 28 June 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 6 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 37s
Average length
52s

Measured directly from 3 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

62 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 41.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54474082066513541652641.9%
custom 54719970146800305111625.8%
custom 5258249957080579623914.5%
custom 524003072728578636234.84%
custom 534179971107654190534.84%
custom 544982266976143721534.84%
custom 520395380086330141323.23%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

Measured over the 6 most recent posts we hold, published 28 June 2026 to 23 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

23 Jul 2026, 08:08 UTC95 views12 reactionsread 8 August 2026
Forwarded from @gdetotamusicPhoto

Пленэр — это красиво, даже если в первый раз. «Так и научится рисовать можно!» — цитирую слова Наташи 🤍 Живописные подсъёмы и декоративное дерево @berggphoto . . . Чтобы присоединиться к нашей компании, пиши @sashagdetotam

custom 54474082066513541655custom 53417997110765419053custom 52039538008633014132custom 52582499570805796231custom 54498226697614372151

19 Jul 2026, 18:04 UTC146 views11 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54474082066513541656custom 52582499570805796233custom 54498226697614372152

19 Jul 2026, 17:31 UTC143 views7 reactionsread 8 August 2026
Video

Video, posted without a caption

custom 54474082066513541655custom 52582499570805796232

19 Jul 2026, 17:14 UTC130 views11 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54474082066513541659custom 52582499570805796232

18 Jul 2026, 14:15 UTC151 views6 reactionsread 8 August 2026
Forwarded from @polynaxrenblunPhoto

Ребята, демонстрирую помещение, в котором будет проходить мой воркшоп! Познакомилась с пространством и Юлей, которая всё показала и рассказала о Домике 44. О домике узнала от своей заказчицы и творческой коллеги Светы @LUTYIZVER , которая участвовала в создании сей прекрасного места и продолжает обучать и творить тут для творческих людей. Пространство супер, локация тоже. Доделываю афишу и буду делать анонс! Зап

custom 54719970146800305114custom 52582499570805796231custom 54474082066513541651

28 Jun 2026, 12:06 UTC244 views15 reactionsread 8 August 2026
Forwarded from @svoi_v_gorakhVideo

🟧4 июля, суббота Закат над морем и живая музыка под открытым небом✨ В этот вечер для нас выступят Вика Победа и Светлана Берг — авторы-исполнители, которые объединят свои голоса в программе из авторских песен и любимых каверов. Гитара, перкуссия и искренние истории в музыке создадут настроение теплого летнего вечера, которым хочется наслаждаться без спешки. Приходите с любимыми людьми или присоединяйтесь сами — сре

custom 547199701468003051112custom 52400307272857863623

Showing the 6 most recent of 6 posts we hold for @berggphoto. 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.

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

“Летопись Лютого Зверя” (@berggphoto), 298 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/berggphoto.

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.