Channel

BAROCO | WYZWYZ

@baroco

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

2,879subscribers

+52 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	-1002119277054
Type	Channel
Username	@baroco
Created	10 December 2023 — measured — dated from the channel’s first post
First recorded	7 August 2026
Last confirmed live	28 August 2026
Measurements held	10
Confirmed unchanged	1 time, most recently 28 August 2026
On Telegram	t.me/baroco

Growth

10 measurements spanning 22 days, net +52. 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 2,818–2,887 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
28 Aug 2026, 19:38	2,879	+5
25 Aug 2026, 16:49	2,874	-1
22 Aug 2026, 23:15	2,875	-1
19 Aug 2026, 17:42	2,876	+10
16 Aug 2026, 17:46	2,866	+9
13 Aug 2026, 05:06	2,857	+13
10 Aug 2026, 12:54	2,844	+18
7 Aug 2026, 11:11	2,826	-1
7 Aug 2026, 03:30	2,827	no change
7 Aug 2026, 03:18	2,827	first reading

Engagement

4 posts held, back to 10 December 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pagesof 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 4 posts for this entry, the most recent from 17 July 2025. An engagement rate over an empty window would be a number about nothing.

Citation-graph rank

Citation-graph rank — 770 of 1,624,174entries 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.

Mentions

Named by 525 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.

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

“BAROCO | WYZWYZ” (@baroco), 2,879 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/baroco.

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.