Telegram RegisterThe public register of Telegram
Telegram profile photo for DDR NanoTech

Channel

DDR NanoTech

@ddrnanotech

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

72subscribers

+1 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-1001270783025
TypeChannel
Username@ddrnanotech
CreatedBetween 1 March 2018 and 14 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/ddrnanotech

Growth

7173727 August 2026 — 71 subscribers9 August 2026 — 71 subscribers15 August 2026 — 73 subscribers22 August 2026 — 71 subscribers29 August 2026 — 72 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net +1. 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 71–73 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 12:2572+1
22 Aug 2026, 20:0371-2
15 Aug 2026, 16:0773+2
9 Aug 2026, 23:1671no change
7 Aug 2026, 08:2271first reading

Engagement

20 posts held, back to 14 August 2021the 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.

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 4 December 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Dec 2022, 08:25 UTC≈1,010 viewsread 9 August 2026
Forwarded from @ntcomputerPhoto

Gigabyte Aorus DDR5 32 gb (2×16 gb) 5200 MHz - 188 y.e.

4 Dec 2022, 05:49 UTC≈3,630 viewsread 9 August 2026
Photo

🔲DDR5 16 GB Kingston FURY 5200 MHz - 78 y.e. 🔲DDR5 16 GB Kingston FURY 5600 MHz - 133 y.e. 🔲DDR5 32GB Gigabyte Aorus (2x16gb) 5200 MHz - 188 y.e. 🔲DDR5 8Gb/4800 Crucial - 41 y.e 🔲DDR5 16Gb/4800 Crucial - 66 y.e. 🔲DDR5 16G/4800 Lexar Ares - 73 y.e. 🔲DDR5 32G(16*2)/5200 Lexar Ares - 171 y.e. 🔲DDR5 8Gb/5200 Kingston RGB - 50 y.e. 🔲DDR5 32Gb/6000 Kingston Renegate RGB - 231 y.e.

16 Apr 2022, 13:39 UTC≈3,620 viewsread 9 August 2026
Photo

SoDDR4 16Gb/3200 Lexar - 56 y.e. SoDDR4 16Gb/3200 Crucial - 56 y.e. DDR4 8Gb/3200 Lexar - 28 y.e. DDR4 8GB/3200 Crucial - 28 y.e.

19 Mar 2022, 11:52 UTC≈3,750 viewsread 9 August 2026
Photo

1)DDR 5 16 GB Kingston FURY 5600 - 155 y.e. 2)DDR5 32(16*2)Kingston FURY 5600 -290 y.e. 3)DDR5 16 GB Kingston FURY 4800 - 140 y.e. 4)DDR5 32(16*2)Kingston FURY 4800 - 255 y.e.

8 Dec 2021, 11:14 UTC≈3,550 viewsread 9 August 2026
Photo

Corsair Vengerance LPX DDR4 32gb (2×16gb) 3600MHz - 168 y.e.

8 Dec 2021, 10:36 UTC≈1,410 viewsread 9 August 2026
Photo

G.SKILL Ripjaws V ddr4 32gb 3200 Mhz (2x16gb) - 155 y.e.

2 Dec 2021, 11:07 UTC≈1,590 viewsread 9 August 2026
Forwarded from @ntcomputerPhoto

RipjawsV DDR4 8GB 3600 (16GB) kit - 115 y.e

16 Oct 2021, 13:58 UTC≈6,630 viewsread 9 August 2026
Photo

G.SKILL Ripjaws V ddr4 32gb 3200 Mhz (2x16gb) - 155 y.e.

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“DDR NanoTech” (@ddrnanotech), 72 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/ddrnanotech.

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.