Blog

Archive Accounts 2012–2020: a Range, Not an Exact Date

The Nordi catalogue holds exactly two positions with the age label Aged 2012–2020 — this is the deepest registration date in the whole catalogue. The key thing about this label: what is written down is a range, not a particular year, and there are eight years between its edges. Below: what follows from that when ordering, where this step stands relative to the rest of the age ladder, and what the age label does not say at all.

A range instead of a date: what that changes

Age is written in the catalogue in three different ways, and the range is the widest of them. Alongside it, in the same section of auto-registered accounts, stand exact dates of the form Reg. 03.2026 or Reg. 2023 and holding periods of the form Aged 7+ months. A range works differently: it sets the boundaries inside which the registration dates of the accounts in the batch lie, but not a particular value for each of them.

  • Both boundaries are set by the label itself — 2012 and 2020. The label implies no dates outside that interval.
  • The year inside the range is not chosen: the order goes by the age label as a whole, there is no separate year field in the listing.
  • The batch is not uniform by date — the spread between the edges is eight years.
  • Such a batch can be compared with a position that carries an exact date like Reg. 28.05.2024 only by the boundaries of the range.

The practical conclusion is simple: if the task requires a known year for every account, the range does not close it — for that the catalogue has positions with an exact registration date.

Where this step stands in the age ladder

The ladder runs from a fresh registration to the archive. Below is a snapshot of the catalogue as of 19.08.2026: one characteristic position per step, prices and minimum batches verbatim from the listings.

Age stepCatalogue positionPriceMin. batchFormat
FreshMobile API autoreg | Fresh | Direct | ENG6.71 ₽100Login:Pass | Cookie
Aged 2+ monthsSMS API autoreg | Reg. 06.2026 | 2FA | 100% Valid24.89 ₽10Login:Pass:2FA_code | Cookie
Aged 5+ monthsAPI autoreg | Reg. 03.2026 | NoFrozen17.05 ₽36IGAM
Aged 7+ monthsAPI autoreg | Reg. 01.2026 | 2FA23.85 ₽10IAM
Aged 450+ daysAPI autoreg | V331.05 ₽30IAM
Aged | Reg. 2023API autoreg | 2FA | NoFrozen52.82 ₽10IGAM
Aged 2012–2020API autoreg | 2FA109.3 ₽10IAM
Aged 2012–2020API autoreg | 2FA | Firstmail120.11 ₽10IAM

Two observations on the table. First: the order of prices does not repeat the order of age row by row — the position «Aged 5+ months» at 17.05 ₽ is cheaper than «Aged 2+ months» at 24.89 ₽, because they differ not only in holding time but also in format, labels and minimum batch. Second: a noticeable gap appears where months give way to years — the step Reg. 2023 costs 52.82 ₽, the archive one 109.3 ₽, that is, about sixteen times more than the cheapest fresh position at 6.71 ₽.

Even so, the archive is not the most expensive item in the catalogue: the Manual reg position with the label Aged 24+ months costs 268.61 ₽. But there the method of registration is different, and so is the age label; in the depth of the registration date itself there is nothing above Aged 2012–2020 in the catalogue.

What the age label does not say

Age here is about the registration date, and only about it. Not a single position in the catalogue has fields about posts, followers, the avatar or how filled-in the profile is, so there are no such data either in the listing of the archive batch or in this text. The label means that the accounts were created in the period 2012–2020 — and nothing beyond that.

This is visible from the catalogue itself. The only label that touches the content of a profile at all is Empty on the Manual reg position at 268.61 ₽. The archive batches have no such field, just as they have no other field about the history of an account. Even the separate line of real accounts at 57.99 ₽ comes with the label Fresh: an axis of “what happened to the profile” simply does not exist in the catalogue.

Hence the rule: if the task depends on the content of a profile, the age label does not solve it — it answers a different question. But if what is needed is exactly the seniority by date, it answers precisely and verifiably, because the date is fixed in the name of the position.

Stock counted in units and the minimum batch

The archive is the smallest part of the catalogue by volume. The total stock across the two positions is 1594 units: 1498 in the batch without mail and 96 in the batch with the label Firstmail. For comparison, the whole section of auto-registered accounts with aging is 31 positions and 236 705 units of stock.

  • The minimum batch for both archive positions is 10 units; instantly available are 200 and 96 units respectively.
  • The minimum in the catalogue is counted as the larger of two: the supplier’s minimum for the position, and the quantity that reaches the order threshold of 600 ₽. For positions with instant delivery the 600 ₽ threshold does not apply — the supplier’s minimum works, those same 10 units.
  • A stock of 96 units in the batch with Firstmail is less than ten minimum batches: a large volume on this particular row cannot be assembled.
  • The figures above are a snapshot as of 19.08.2026. The stock is counted in units and it moves; the current values always stand in the listing of the position, not in an article.

The IAM format: what arrives in the delivery

For both archive positions the last field of the name is Format: IAM. This is an export for InstAccountsManager: the batch is imported into the manager, and the familiar login:pass line will not be in the file. There are no other formats on the archive step at the moment — a choice between IAM and something else does not exist here.

On the neighbouring steps the formats are different: fresh positions have Login:Pass | Cookie, part of the aged ones have Login:Pass:2FA_code | Cookie or IGAM. That is, moving to the archive step may also mean a change of the delivery format, and this is worth checking before payment. The decodings of the labels and formats from the names of positions are collected in the label reference.

Summary

Aged 2012–2020 is a range of registration dates eight years wide, the deepest age step in the catalogue and at the same time the smallest by stock: two positions at 109.3 ₽ and 120.11 ₽, 1594 units between them, both through API autoreg, with the 2FA label and in the IAM format. The year inside the range is not chosen, the history of a profile is not described by the label, and the volume is limited by the stock. If it is exactly the depth of the date that is needed, see Archive accounts 2012–2020; if depth is not critical, the neighbouring steps are noticeably cheaper — from 6.71 ₽ for fresh auto-registered accounts.

FAQ

No. The name of the position carries the range «Aged 2012–2020», there is no separate year field in the catalogue, and the order goes by the age label as a whole.