Summary

  • STELLANOR DATACENTERS PROPERTIES UK III LIMITED is an active British company incorporated in 2002. The exact company number, 04592242, links the new name to the former 4D Data Centres business rather than to a newly formed shell.
  • RIPE records provide unusually useful continuity evidence: the exact legal name and company number appear on a Local Internet Registry (LIR) organisation record that retains a 4D maintainer. Related route records point towards the historic 4D network, but the public ASN registration still points to a different organisation record and a Redcentric maintainer, so resource control should be confirmed rather than assumed.
  • Stellanor presents an eleven-site UK platform with carrier-neutral connectivity, migration help, named site support and customer portals. Those are credible operating signals at group level; contracts, service levels, locality controls and escalation ownership still need to identify the entity responsible for each promise.

A 2002 company with a 2026 name

The Roman numeral in STELLANOR DATACENTERS PROPERTIES UK III LIMITED makes the company sound like a recent acquisition vehicle. The public record tells a more useful story. Companies House identifies company 04592242 as active, incorporated on 15 November 2002 and classified under other information technology service activities. It traded first as 4D Internet Limited and, from March 2007 until May 2026, as 4D Data Centres Limited.

That continuity matters. A buyer is not looking at a name that appeared without history; the same registration has more than two decades behind it. Yet age alone is not an uptime certificate. It says that the legal identity persisted, not that every facility, employee, control or customer contract remained unchanged.

The timing of the transition is more revealing. The filing history records a name-change resolution dated 30 April 2026 and a certificate issued on 13 May. On 30 April, Peter Brotherton and Lee Morley left the board, while Gary Watson and Howard Pheby joined. The current officer page lists Watson and Pheby as the two active directors. This is a visible governance handover, not merely a new sign above the door.

BTW's directory entry is deliberately modest: it identifies a private company connected to internet infrastructure and marks its status as not yet assessed. Corporate and registry evidence can now sharpen that starting point, while preserving the distinction between verified identity and operating assurance.

The acquisition explains the handover, but not every boundary

Stellanor announced on 5 May 2026 that it had completed the acquisition of eight data centres from Redcentric. The company said those sites served about 450 enterprise customers and took its platform to eleven UK locations with 39 MVA of secured grid capacity. The announcement came days after the director changes at company 04592242 and shortly before its new name became effective.

The sequence strongly supports the inference that the former 4D company entered Stellanor's acquired estate. It does not, by itself, define the vehicle's whole role. The legal name includes "Properties", Companies House gives it an IT-services classification, and Stellanor markets services through a group brand. Public material does not settle whether this company owns a particular freehold or lease, employs site staff, contracts with every customer, operates network equipment, or performs some combination of those functions.

That distinction is practical. A customer evaluating colocation may face several accountable entities: a property holder, a service company, a network operator and a group parent. The right diligence question is not simply "Is this Stellanor?" It is "Which company signs, which company operates, and which company remains responsible when power, cooling, connectivity or support falls outside specification?"

RIPE records show continuity and a live attribution gap

The strongest technical identity record is RIPE organisation ORG-DCL10-RIPE. It gives the exact Stellanor UK III name, country code GB and registration number 04592242. It classifies the organisation as an LIR, records an address at Sirius II, 122 Oyster Lane in Byfleet, and retains MNT-4DDATACENTRES as a maintainer reference. The record was last modified on 20 May 2026, after the corporate rename.

This is better evidence than a loose brand match. The legal number, old operational maintainer and post-acquisition update connect the renamed company to a real internet-registry identity. Stellanor's site list also names its Byfleet facility at 122 Oyster Lane, giving the registry address a visible place in the current estate.

The network trail then becomes less tidy. An inverse RIPE query for the legacy maintainer surfaces many route objects associated with the former 4D estate, including aggregate IPv4 routes such as 109.74.20.0/22 and 178.17.32.0/20, plus the IPv6 route 2a00:1c18::/29. Those entities commonly specify AS31463 as origin. But the public RIPE record for AS31463 names FourD-AS while pointing to the different organisation record ORG-RSL38-RIPE and a Redcentric maintainer. Its last modification was in December 2024, before the Stellanor transaction.

This does not prove a problem. Registry records, commercial ownership and operational handovers often move on different clocks. It does mean that the public evidence cannot yet assign AS31463 or every maintained route directly to company 04592242. A serious customer should request a current prefix and ASN schedule, the responsible LIR and network operations contact, routing-security ownership, upstream and peering dependencies, and the incident path when a route is filtered or withdrawn. Registry evidence is a powerful continuity signal, but it is not a substitute for a current responsibility matrix.

The service surface is substantial, and mostly group-level

Stellanor's public site gives a concrete operating surface. It lists eleven facilities across London, Byfleet, Cambridge, Gatwick, Hemel Hempstead, Reading, West Yorkshire and Woking. Its connectivity material describes cloud- and carrier-neutral facilities, presents a per-site carrier selector, and offers internet exchange, IP transit and fibre options. That is service proof in the sense that a buyer can inspect locations, access paths and product categories rather than relying on a corporate name alone.

It is still supplier-authored evidence. A carrier shown in a selector may be present at one site but not another; presence does not define lead time, diversity, capacity or contractual recourse. The same caution applies to Stellanor's claim that coordinated upgrades will add high-density power, cooling and fibre capabilities for machine-learning and real-time analytics workloads. The announcement describes a programme across the platform, not the completed state of every hall.

The right next step is site-specific proof: current single-line power diagrams, cooling design and operating envelope, carrier entry points, cross-connect process, maintenance history, capacity available for the proposed deployment, and the service schedule that binds those features. The public record makes such a request reasonable and specific. It does not make the answer automatic.

UK locations help with locality, but do not settle sovereignty

An eleven-site UK footprint offers a useful architectural choice. Enterprises can place primary and recovery equipment near users, teams or regulated operations without defaulting to a single London campus. For latency-sensitive services and physical access, regional facilities can matter as much as a headline capacity number.

Physical location is only one layer of data sovereignty. A UK cabinet does not reveal where backups, telemetry, support records, portal data or security logs are processed. Nor does it identify who can administer a system from abroad, which subcontractors can enter the service chain, or whether a recovery design crosses a jurisdiction. Colocation customers also retain responsibility for many of their own systems, so facility locality and application-data control should not be conflated.

A defensible locality statement therefore needs named sites, data categories, replication paths, remote-access rules, support locations and deletion obligations. It should also name the contracting and operating entities. Stellanor's geographic spread makes a UK-local design plausible; only the final architecture and agreement can make it true for a particular workload.

Support promises need both people and systems

Stellanor says its support team provides direct specialist contact around the clock rather than a call-centre layer. It promises a Customer Success Manager, a dedicated Site Manager, a ticketing system, the myStellanor self-service portal and a CIMS portal for energy insight. Its migration service describes preparation, coordinated moves, post-migration testing and ongoing support setup.

This combination of local labour and software is sensible. Portals can make requests, orders and energy use visible; named people can interpret an incident and coordinate work that cannot be automated. Neither should be treated as a replacement for the other. A dashboard does not establish response authority, while a personal-support promise does not establish measurable availability.

Customers should pin down staffed hours at the chosen site, remote-hands scope, after-hours access, spare-parts arrangements, response and resolution targets, severity definitions, escalation roles and the fallback channel if a portal is unavailable. The two active directors also hold visible group roles, Watson as managing director and Pheby as chief commercial officer, according to Stellanor's management page. That alignment supports accountability at a senior level, but operational escalation still belongs in the service documents.

What the evidence allows a buyer to say

Three confidence levels keep the conclusion honest. Established facts include the exact legal identity, its 2002 incorporation, its former 4D names, the April 2026 board handover, its post-rename RIPE LIR record and the Byfleet address shared by that record and Stellanor's facility list. Stellanor's own material also establishes what the group publicly offers and claims across its UK platform.

A strong but bounded inference is that company 04592242 provides continuity from 4D Data Centres into the Stellanor estate acquired from Redcentric. The date sequence, directors, legal name, LIR update and site address all point in the same direction. What remains unproven in the frozen public evidence is the exact allocation of property, customer contracts, staff, ASNs, prefixes and service obligations among this company and other Stellanor entities.

That is not a reason to dismiss the business. It is a reason to buy against identified responsibilities. Treat the company number as the anchor, registry records as technical evidence, site documents as facility evidence, and signed schedules as the final source for service, locality and support commitments. The Stellanor name opens the inquiry; assurance comes from making those layers agree.