Channel

Arc Bridge Alerts

@arcbridgealers

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

190subscribers

-5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID	-1004364219787
Type	Channel
Username	@arcbridgealers
Created	Between 1 June 2026 and 3 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	11 September 2026
Measurements held	8
Confirmed unchanged	1 time, most recently 11 September 2026
On Telegram	t.me/arcbridgealers

Growth

8 measurements spanning 37 days, net -5. 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 188–198 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
11 Sept 2026, 23:57	190	+1
3 Sept 2026, 06:08	189	-3
26 Aug 2026, 07:02	192	-5
19 Aug 2026, 14:02	197	+1
13 Aug 2026, 05:05	196	+2
7 Aug 2026, 05:48	194	no change
6 Aug 2026, 17:10	194	-1
6 Aug 2026, 09:22	195	first reading

Engagement

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

Recent posts

6 Aug 2026, 20:57 UTC16 viewsread 7 August 2026

💤 Daily heartbeat: watcher alive at Arc block 11356053. No bridge events in the last 24h. Your transfer: pending_confirmations (still queued).

6 Aug 2026, 16:20 UTC27 viewsread 7 August 2026

🔥 2,000.00 USDC just bridged from Avalanche into the Arc queue from 0x5472…baf7 → burn tx ⏳ queue now 1,169,546.13 USDC · sidoor.trade

6 Aug 2026, 15:58 UTC29 viewsread 7 August 2026

🔥 10.00 USDC just bridged from Base into the Arc queue from 0xba24…646f → burn tx ⏳ queue now 1,169,546.13 USDC · sidoor.trade

5 Aug 2026, 20:56 UTC40 viewsread 7 August 2026

💤 Daily heartbeat: watcher alive at Arc block 11356053. No bridge events in the last 24h. Your transfer: pending_confirmations (still queued).

5 Aug 2026, 17:06 UTC44 viewsread 7 August 2026

🔥 10.00 USDC just bridged from Arbitrum into the Arc queue from 0xb3fa…f3f0 → burn tx ⏳ queue now 1,169,534.03 USDC · sidoor.trade

4 Aug 2026, 20:56 UTC47 viewsread 7 August 2026

💤 Daily heartbeat: watcher alive at Arc block 11356053. No bridge events in the last 24h. Your transfer: pending_confirmations (still queued).

4 Aug 2026, 20:21 UTC81 viewsread 7 August 2026

🐋 🔥 62,771,017,353,866,810,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00 USDC just bridged from Ethereum into the Arc queue from 0x0000…0000 → burn tx ⏳ queue now 1,169,527.76 USDC · sidoor.trade

4 Aug 2026, 20:21 UTC51 viewsread 7 August 2026

4 Aug 2026, 20:21 UTC50 viewsread 7 August 2026

4 Aug 2026, 20:21 UTC46 viewsread 7 August 2026

4 Aug 2026, 20:21 UTC43 viewsread 7 August 2026

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

Mentions

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

Named by

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

Open Interest
@OI_Delta · 5,3322 posts Crypto Minister
@crypto_minister · 4,6611 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“Arc Bridge Alerts” (@arcbridgealers), 190 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/arcbridgealers.

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.