Telegram RegisterThe public register of Telegram
Telegram profile photo for PulseChain Dev Activity

Channel

PulseChain Dev Activity

@pulsedevactivity

On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

415subscribers

-5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001633605835
TypeChannel
Username@pulsedevactivity
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/pulsedevactivity

Growth

415420417.57 August 2026 — 420 subscribers7 August 2026 — 420 subscribers15 August 2026 — 419 subscribers23 August 2026 — 415 subscribers7 August 202623 August 2026
4 measurements spanning 16 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 414–421 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 05:03415-4
15 Aug 2026, 05:15419-1
7 Aug 2026, 02:01420no change
7 Aug 2026, 01:49420first reading

Engagement

20 posts held, back to 16 June 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
15.7%
avg views ÷ 415 subscribers
Avg views / post
65.3
7 posts measured
Reaction rate
3.23%
reactions ÷ views · ER floor
Posts in window
7
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 4 of 7 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 4 August 2026
Posts held20 (16 June 20264 August 2026)
Views total457
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:01 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.

Reaction mix

17 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 29.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩529.4%
👎423.5%
🔥423.5%
🗿423.5%

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 8 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 17reactions 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 16 June 2026 to 4 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

4 Aug 2026, 00:30 UTC36 views1 reactionsread 7 August 2026

PulseChain activity Bret commented on issue #37 at PulseChain / PulseChain Mainnet Restored by the moderation bot: this comment was removed in error during an automated review of the project's history, and is reinstated here with its original author credited. Originally posted by @cfreeman4 (https://gitlab.com/cfreeman4): IT WORKED!!!!! So I've been reading about spiking the gas prices beyond normal limits and I

🗿1

1 Aug 2026, 23:26 UTC174 views2 reactionsread 7 August 2026

PulseChain activity GIGA commented on issue #267 at PulseChain / PulseChain Mainnet (https://gitlab.com/-/project/45984690/uploads/481ed3a68649de6de32aeabb38c17a99/bretepisagayniggerfaggot.gif) 2026-08-01 23:24:42 +00:00 https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/issues/267#note_3633040913

🔥1🗿1

1 Aug 2026, 21:26 UTC53 views5 reactionsread 7 August 2026

PulseChain activity Bret commented on issue #267 at PulseChain / PulseChain Mainnet It’s a free public RPC. No information about the rpc will be shared. You can use it or you can run your own (which is the superior way to run an RPC). 2026-08-01 21:23:40 +00:00 https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/issues/267#note_3632924175

💩3👎1🗿1

1 Aug 2026, 21:13 UTC50 viewsread 7 August 2026

PulseChain activity Crypto StarterAcademy commented on issue #267 at PulseChain / PulseChain Mainnet Thanks, Bret. That confirms that the endpoint is available for public use. To keep our monitoring conservative and avoid placing unnecessary load on the service, could you please confirm whether there are any published or recommended: rate or concurrency limits; timeout, batch or response-size limits; restrictions

1 Aug 2026, 21:05 UTC47 views2 reactionsread 7 August 2026

PulseChain activity Bret commented on issue #267 at PulseChain / PulseChain Mainnet It’s a public RPC just use it. 2026-08-01 21:03:19 +00:00 https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/issues/267#note_3632902897

💩2

1 Aug 2026, 21:05 UTC49 viewsread 7 August 2026

PulseChain activity Bret closed issue #267: Permission and limits for low-frequency read-only PulseChain RPC monitoring at PulseChain / PulseChain Mainnet 2026-08-01 21:02:53 +00:00 https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/work_items/267

1 Aug 2026, 20:59 UTC48 viewsread 7 August 2026

PulseChain activity Crypto StarterAcademy opened issue #267: Permission and limits for low-frequency read-only PulseChain RPC monitoring at PulseChain / PulseChain Mainnet 2026-08-01 20:55:39 +00:00 https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/work_items/267

23 Jul 2026, 00:46 UTC75 viewsread 7 August 2026

PulseChain activity sjb933 pushed to project branch master at PulseChain / PulseChain Mainnet sjb933 (192dafa9) (https://gitlab.com/pulsechaincom/pulsechain-mainnet/-/compare/873716af300a7ea4612423d5fb5fb7093bd0a9ad...192dafa9e99b33eab2456edbaae93159a34bb8a5) at 23 Jul 00:44 Add a pasteable AI agent prompt for first-time node setup. ... and 2 more commits 2026-07-23 00:44:19 +00:00 https://gitlab.com/pulsech

21 Jul 2026, 01:26 UTC62 viewsread 7 August 2026

PulseChain activity Bret pushed to project branch master at PulseChain / hex-server Bret (2b890987) (https://gitlab.com/pulsechaincom/hex-server/-/commit/2b8909870f905e12ab8e50ed1877773c3b4ab273) at 21 Jul 01:23 Update release version v2.1.2 2026-07-21 01:23:52 +00:00 https://gitlab.com/pulsechaincom/hex-server/-/commit/2b8909870f905e12ab8e50ed1877773c3b4ab273

21 Jul 2026, 01:26 UTC72 views1 reactionsread 7 August 2026

PulseChain activity Bret pushed new project tag v2.1.2 at PulseChain / hex-server Bret (54144c01) (https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.2) at 21 Jul 01:23 Update release version v2.1.2 2026-07-21 01:23:53 +00:00 https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.2

👎1

17 Jul 2026, 02:35 UTC70 viewsread 7 August 2026

PulseChain activity Bret pushed to project branch master at PulseChain / hex-server Bret (c5c95525) (https://gitlab.com/pulsechaincom/hex-server/-/commit/c5c95525a0c5f8df5e1840950bb426c5ad6ed762) at 17 Jul 02:33 Update release version v2.1.1 2026-07-17 02:33:26 +00:00 https://gitlab.com/pulsechaincom/hex-server/-/commit/c5c95525a0c5f8df5e1840950bb426c5ad6ed762

17 Jul 2026, 02:35 UTC78 views1 reactionsread 7 August 2026

PulseChain activity Bret pushed new project tag v2.1.1 at PulseChain / hex-server Bret (fbfb1829) (https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.1) at 17 Jul 02:33 Update release version v2.1.1 2026-07-17 02:33:28 +00:00 https://gitlab.com/pulsechaincom/hex-server/-/commits/v2.1.1

👎1

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

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

“PulseChain Dev Activity” (@pulsedevactivity), 415 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/pulsedevactivity.

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.