Telegram RegisterThe public register of Telegram
Telegram profile photo for Bobroyasher's lodge

Channel

Bobroyasher's lodge

@Bobroyashers_lodge

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

29subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002721683099
TypeChannel
Username@Bobroyashers_lodge
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 11 September 2026
On Telegramt.me/Bobroyashers_lodge

Growth

293029.510 August 2026 — 29 subscribers11 August 2026 — 29 subscribers26 August 2026 — 30 subscribers3 September 2026 — 29 subscribers10 August 20263 September 2026
4 measurements spanning 24 days. 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 29–30 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 08:3329-1
26 Aug 2026, 01:0430+1
11 Aug 2026, 04:4629no change
10 Aug 2026, 02:3229first reading

Engagement

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

Reaction mix

47 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 34.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1634.0%
❤‍🔥1021.3%
🥰1021.3%
🍓510.6%
💘36.38%
🔥12.13%
😍12.13%
😭12.13%

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

Measured over the 11 most recent posts we hold, published 13 July 2026 to 7 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

7 Aug 2026, 09:02 UTC13 views3 reactionsread 11 August 2026
Photo

До осознания неописуемого ужаса 5 минут #Бушующийветер@Bobroyashers_lodge #Дилан@Bobroyashers_lodge #OC

💘3

5 Aug 2026, 09:03 UTC16 views6 reactionsread 11 August 2026
Photo

Смущашка #Бушующийветер@Bobroyashers_lodge #Федар@Bobroyashers_lodge #OC

🥰51

27 Jul 2026, 09:02 UTC27 views3 reactionsread 11 August 2026
Photo

Атака на HOUNDTOMBS Поняшка-пиратяшка #Artfight #Artfight_2026 #OC

2😍1

25 Jul 2026, 09:01 UTC27 views5 reactionsread 11 August 2026
Photo

Атака на FreesthatHD Я любительница белых змей, вы ж знаете) #Artfight #Artfight_2026 #OC

❤‍🔥3🥰2

23 Jul 2026, 09:05 UTC26 views5 reactionsread 11 August 2026
Photo

Биг бьютифул мэн Гольд #Бушующийветер@Bobroyashers_lodge #Гольд@Bobroyashers_lodge #OC

❤‍🔥41

21 Jul 2026, 11:22 UTC24 views3 reactionsread 11 August 2026
Photo

Усатик Федар. Юнга #Бушующийветер@Bobroyashers_lodge #Федар@Bobroyashers_lodge #OC

🥰21

19 Jul 2026, 10:01 UTC23 views3 reactionsread 11 August 2026
Photo

Замерзла бедняжечка #OC #DnD #ITVG@Bobroyashers_lodge #Yuanti #Юсса@Bobroyashers_lodge

2😭1

17 Jul 2026, 09:01 UTC23 views3 reactionsread 11 August 2026
Photo

Красавчик Стардаст. Атака на ZodyZaible #Artfight #Artfight_2026 #OC

3

15 Jul 2026, 11:02 UTC23 views4 reactionsread 11 August 2026
Photo

Сеанс гирудотерапии #Бушующийветер@Bobroyashers_lodge #Димитрий@Bobroyashers_lodge #Степан@Bobroyashers_lodge #Борис@Bobroyashers_lodge #OC

4

14 Jul 2026, 09:20 UTC28 views5 reactionsread 11 August 2026
Photo

Влетаю в #PortfolioDay Рисую скетчики и яркие картинки, нарисованные акриловыми и спиртовыми маркерами

❤‍🔥32

13 Jul 2026, 11:03 UTC572 views7 reactionsread 11 August 2026
Photo

Ревендж для Митери Зеркалка на зимний рисуночек. Митя успела порадоваться морозам, пора и Альберте порадоваться тёплым денькам #Artfight #Artfight_2026 #OC

🍓5🔥1🥰1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Bobroyasher's lodge” (@Bobroyashers_lodge), 29 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/Bobroyashers_lodge.

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.