BIZTRAC BETA
COMPANY REGISTER PROFILE
926139630 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Computer programming activities

SECONDGO AS

Org. no. 926139630 Limited company (AS) Ringsaker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 50,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-09-09 Avregistrert registrert 2026-09-09.

SECONDGO AS is registered as a limited company in Ringsaker, Innlandet with organisation number 926139630. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 60000 shares. The company's stated purpose is: “Utvikling og drift av digitale tjenester.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 50,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SECONDGO AS?

No shareholders are registered for SECONDGO AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SECONDGO AS

Where is SECONDGO AS based?

SECONDGO AS has its business address in Lismarka.

Property

Business address Sjusjøvegen 997, 2616 Lismarka
Cadastral unit 3411-489/4/0/0
Building Våningshus · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.