Telegram RegisterThe public register of Telegram
Telegram profile photo for Облако (склад) by RB

Channel

Облако (склад) by RB

@RaeBaBae

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

1,358subscribers

-13 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001365661749
TypeChannel
Username@RaeBaBae
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/RaeBaBae

Growth

1,3571,3711,3646 August 2026 — 1,371 subscribers6 August 2026 — 1,371 subscribers7 August 2026 — 1,370 subscribers10 August 2026 — 1,371 subscribers14 August 2026 — 1,368 subscribers17 August 2026 — 1,362 subscribers23 August 2026 — 1,360 subscribers26 August 2026 — 1,358 subscribers30 August 2026 — 1,357 subscribers6 September 2026 — 1,358 subscribers1,3586 August 20266 September 2026
10 measurements spanning 31 days, net -13. 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 1,355–1,373 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 13:011,358+1
30 Aug 2026, 08:431,357-1
26 Aug 2026, 22:441,358-2
23 Aug 2026, 22:341,360-2
17 Aug 2026, 12:021,362-6
14 Aug 2026, 07:551,368-3
10 Aug 2026, 15:021,371+1
7 Aug 2026, 13:561,370-1
6 Aug 2026, 20:021,371no change
6 Aug 2026, 19:541,371first reading

Engagement

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

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥266.7%
👍133.3%

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 2 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 3 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 20 July 2026 to 5 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

5 Aug 2026, 21:52 UTC68 views1 reactionsread 6 August 2026
Forwarded from @monogram_androidFile

File, posted without a caption

👍1

Signed 𝕏

5 Aug 2026, 21:52 UTC66 viewsread 6 August 2026
Forwarded from @monogram_android

v0.3.0 Changelog: - Added support for text above and below media files - Rewrote GMS push notification logic - Rewrote file downloading - Rewrote the app cache tab so it now clears everything properly - Reworked the Premium tab - Made significant improvements to message sending - Improved profile loading and behavior - Speeded up delivery of various events - Reduced ad banner size - Improved preloading of newer and

Signed 𝕏

31 Jul 2026, 16:39 UTC169 views2 reactionsread 6 August 2026
Forwarded from @exteraGramPhoto

✈️ exteraGram 12.9.0 • Download • Screenshots • exteraGram Forum • Support Development 🇺🇸 EN: – Channel Feed: all posts from your channels in a single timeline. – More Material 3 Design: redesigned chat header, floating navigation bar, sliders, switches, loaders and predictive back animation. – Liquid Glass message menu and reactions panel, plus an outline style selector: glare, solid or hidden. – CameraX update: a

❤‍🔥2

Signed 𝕏

27 Jul 2026, 14:15 UTC221 viewsread 6 August 2026
Forwarded from @popMODSPhoto

Revanced & Morphe Builder ReVanced & Morphe Builder is an automated build system for creating the latest patched Android apps and Magisk/KernelSU modules. By integrating multiple patch ecosystems and rebuilding releases 24/7, it delivers a fast, reliable, and hassle-free way to stay up to date with the newest enhancements. 🔗 Links: - Download - Screenshots - Features - Source code - Support Group Developer: nullcp

Signed 𝕏

20 Jul 2026, 18:02 UTC320 viewsread 6 August 2026
Forwarded from @monogram_androidFile

File, posted without a caption

Signed 𝕏

20 Jul 2026, 18:02 UTC268 viewsread 6 August 2026
Forwarded from @monogram_android

v0.2.1 Changelog: - Fixed crash when joining channels - Fixed bug causing duplicate media to be sent - Updated TDLib to version 1.8.66 - Implemented Stories support - Added support for dynamic updates of Telegram domain names (t.me, telegram.me, telegram.dog) - Optimized network performance to speed up loading and reduce API errors - Redesigned the fullscreen text editor - Added support for editing messages with ric

Signed 𝕏

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

Mentions

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

“Облако (склад) by RB” (@RaeBaBae), 1,358 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/RaeBaBae.

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.