# nLink Secondary at Oslo: deployment

Canonical ID: `410d17d6-5d9a-43e9-8300-3cede33fe2c5`

Secondary product deployment at nLink operational region.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** nlink-secondary-deployment
- **Status:** operational
- **Model:** [nLink Secondary](/models/nlink-secondary.md) (id: `8262708e-cc9f-4cc7-91a1-628cec2f3075`)
- **Company:** [nLink](/companies/nlink.md) (id: `4fff7f1c-93ce-4eb5-9758-237776878a1d`)
- **Location:** [Oslo](/locations/oslo.md) (id: `03705392-610f-4350-a170-aea1acf1231c`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the nLink Secondary deployment at Oslo?

nLink Secondary, built by nLink, is recorded as a deployment at Oslo on the DEPLOY registry. nLink operates the deployment directly.

### Who operates nLink Secondary at Oslo?

nLink, the manufacturer of nLink Secondary, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the nLink Secondary deployment at Oslo?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/410d17d6-5d9a-43e9-8300-3cede33fe2c5 · feeds: GET /v1/feeds?deploymentId=410d17d6-5d9a-43e9-8300-3cede33fe2c5 · canonical URL: /deployments/nlink-secondary-deployment_