Telegram RegisterThe public register of Telegram

Channel

₁₆₊𝐁𝕽𝐎𝕺𝐊𝐋𝖄𝐍 𝐍𝕺.𝟕ˡⁱᶠᵉ

@brooklynlifee

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

369subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003800079624
TypeChannel
Username@brooklynlifee
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/brooklynlifee

Growth

3698 Aug 2026, 07:46 — 369 subscribers8 Aug 2026, 17:35 — 369 subscribers8 Aug 2026, 07:468 Aug 2026, 17:35
2 measurements taken within a single day. 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 368–370 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:35369no change
8 Aug 2026, 07:46369first reading

Engagement

20 posts held, back to 7 August 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.5%
avg views ÷ 369 subscribers
Avg views / post
64.4
19 posts measured
Reaction rate
11.5%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (7 August 20268 August 2026)
Views total1,224
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
52s
Average length
17s

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

15 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5319100280636218615533.3%
custom 5436217098130988715533.3%
custom 5436027428080228406320.0%
custom 5436003088500561944213.3%

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 areTelegram’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 2 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 15reactions 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 7 August 2026 to 8 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

8 Aug 2026, 04:22 UTC46 views11 reactionsread 8 August 2026

❌✨🔤𝐎𝐎𝕯 𝐍𝕴𝐆𝐇𝐓 🥹 🥹 🕯 : 🔤покойной ночи всем, кроме...❌ 🌟◌ .🥹 𝑳𝒆𝒕'𝒔 𝒉𝒊𝒕 𝒕𝒉𝒆 𝒓𝒐𝒂𝒅, 𝒓𝒂𝒄𝒆𝒓𝒔.. 🤩 🥹тех, кто не любит баунти. ❤️🥹 🥹🤩🥹тех, кто летал на самолёте. ❤️🤩 🤩❤️🥹тех, кому нравятся обезьяны.🥹 🥹❌🤩❌#𝐈𝐧𝐭𝐞𝐫𝐚𝐜𝐭𝐢𝐯𝐞𝐁𝐍𝐍𝐎𝟕❌🤩❤️

custom 53191002806362186154custom 54362170981309887154custom 54360030885005619442custom 54360274280802284061

7 Aug 2026, 21:43 UTC84 views4 reactionsread 8 August 2026
Photo

Говорят, что ночь в Бруклине принадлежит тишине, но мы знаем: она принадлежит тем, кто разрезает её ревом двигателей и светом фар. Наш союз – это идеальный гоночный трек, где каждый участник сохраняет свою траекторию и мощь, но вместе мы создаем динамику, от которой закладывает уши. Мы выбираем партнеров так же придирчиво, как инженер подбирает детали для болида: по чистоте звука, оборотистости и способности держать

custom 54360274280802284062custom 53191002806362186151custom 54362170981309887151

7 Aug 2026, 19:46 UTC93 viewsread 8 August 2026

#𝐁𝐫𝐞𝐚𝐤𝐁𝐍𝐍𝐎𝟕 Разрыв с:: 𝑃𝑎𝑝𝑒𝑟 𝐷𝑜𝑣𝑒𝑠 Пч:: закрытие

7 Aug 2026, 19:36 UTC95 viewsread 8 August 2026

「 🤩 」🔤𝕰𝐏𝕺𝐒𝕿-𝐓𝐈𝕸𝐄 – 🔤𝐔𝕺𝐂𝐇𝕬 . . ⭐️⭐️⭐️⭐️ 𝐬𝐭𝐚𝐫𝐭 ⭐️⭐️⭐️⭐️⭐️⭐️🔄 ⭐️⭐️⭐️⭐️⭐️⭐️⭐️𝐞𝐧𝐝

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

Citation-graph rank

Citation-graph rank — 8,000 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 90 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

𝐔.ۨ𝐍ۧ𝐈ۜ𝐎𝐍۪𝐒 𝐄.ۨ𝐕ۧ𝐎ۜ𝐈𝐑۪𝐄
@evorAMOR · 13
2 posts
𝑉𝐸𝐿𝖵ℰ𝑇 𝑇ℋ𝒪ℛ𝑁 ❬. . ᎒ ㅤ꯭ㅤ꯭𝐿ℒ𝔉ℰ
@lfvelvttrhn · 105
2 posts
[РЕСТ] 𝑀𝑶𝑅𝑇𝑨𝐿 𝑆𝑶𝑈𝑳𝑆 | ʟɪғᴇ
@MSlliff · 50
2 posts
𝗕𝗿𝗶𝗴𝗵𝘁 𝗛𝗮𝘃𝗲𝗻|𝗨𝗻𝗶𝗼𝗻𝘀
@unionsBH · 2
2 posts
♯ ݁ 𝗪𝒊𝒏𝒅𝒃𝒓𝒆𝒂𝒌𝒆𝒓'𝒔┆♯𝗟𝒊𝒇𝒆 ˖ ౨౿
@WBRflood_life · 32
2 posts
Союзы ⋆⁺₊"𝐄𝐦𝐩𝐢𝐫𝐞⟡𝐌𝐚𝐫𝐢𝐭𝐢𝐦𝐞𝄢
@Alliances_empire_martime · 5
1 post
𝐔𝐍𝐈𝐎𝐍𝐒 | 𝐂𝐀𝐑𝐏𝐄 𝐃𝐈𝐄𝐌
@CarpeDiemUnion · 9
1 post
Союзы Муичиро
@conjunctions_QOF · 8
1 post
𓆩𝕺𝐄𝕷𝖀𝐆𝐄 𝖀𝐍𝐈𝕺𝐍𝐒𓆪
@DELUGE_union · 6
1 post
ⲥⲡυⲥⲟⲕ ⲥⲟюⳅⲏυⲕⲟⲃ.
@FRS_Soyuznichki · 2
1 post
𝗧𝗛𝗘 𝗘𝗠𝗣𝗜𝗥𝗘 ℴ𝒻 𝗧𝗛𝗘 𝗩𝗜𝗥𝗢𝗡𝗦 𖧁ִ୧ ֺ 𝅄ᶫᶦᶠᵉ
@life_Virons · 51
1 post
𝑻𝑯𝑬 𝑴𝑶𝑶𝑫𝒀 𝑲𝑵𝒀 ᶫᶦᶠᵉ
@lifethemoodykny · 28
1 post
𝖬𝖾𝖺𝖽𝗈𝗐 𝖺𝗅𝗅𝗂𝖾𝗌
@MDWunion · 2
1 post
. ጠყsᤐֹ᷼ꫀׄdꫀׁׅܻ꯱ָׂˏˏ lꬻfeᦒꬻׂ . .
@msdstiny_life · 14
1 post
ʚ𖦹ɞ 𝐍ℯֺ︩𝐍𝐀𝐃ꪮ ⌗𝗹𝗶𝗳𝗲
@NNDlife · 35
1 post
𝗜𝗡𝗙𝗢 𝗣𝗜𝗥𝗔𝗧 14+
@piraat_info · 313
1 post
𝐿𝑖𝑓𝑒 — 𝐐-𝐒𝐈𝐍𝐆𝐔𝐋𝐀𝐑𝐈𝐒 𖥔 ݁ ˖
@QSingularis_Life · 135
1 post
𝐋𝐈𝐅𝐄 𝐂𝐇𝐀𝐍𝐍𝐄𝐋
@swet_lif · 49
1 post
˖ ࣪ ٬ ุ๋ ⸱ 𓄼 ℑ𝔥𝔯𝔢𝔢 ℌ𝔢𝔞𝔳𝔢𝔫 𝔒𝔣𝔣𝔦𝔠𝔦𝔞𝔩𝔰 ᶫᶦᶠᵉ 𓄹 ˖ ࣪ ٬ ุ๋ ⸱
@thr33_Heaven_0ficcia1ls_lif3 · 109
1 post
UNION/𝙳𝙴𝙼𝙾𝙽𝙸𝙲 𝚂𝙻𝙴𝙴𝙿
@union_demonic · 4
1 post
𝗯𝗹𝗮𝗱𝗲 › 𝘂𝗻𝗶𝗼𝗻𝘀
@unionGalaxysEdge · 5
1 post
﹫ A‌ָ࣪𝗡:ꓷ֕𝐄 ⃟🌺 𝗠ָ࣪𝖠𝖫𝖨֕𝖭ℰ𝖫‌𝖫𝖤 ❜ : 𝐔𝗇𝗂𝗈𝗇𝗌
@unions_AML · 5
1 post
𝗨𝗡𝗜𝗢𝗡𝗦 𝗛𝗔ݔ‌𝖄𝗧𝗜» 𝗖𝗜𝗥𝗖𝗨𝗦
@unions_hayti · 16
1 post
𝙐𝙣𝙞𝙤𝙣𝙨: 𝙈𝙞𝙨𝙩𝙮 𝙋𝙖𝙧𝙖𝙙𝙞𝙨𝙚
@unions_mp · 7
1 post

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

“₁₆₊𝐁𝕽𝐎𝕺𝐊𝐋𝖄𝐍 𝐍𝕺.𝟕ˡⁱᶠᵉ” (@brooklynlifee), 369 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/brooklynlifee.

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.