BIZTRAC BETA
Uoppgitt

IVNETSERIGNER AS

Org. no. 828177532 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 97,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

IVNETSERIGNER AS is registered as a limited company in Oslo, Oslo with organisation number 828177532. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i og forvaltning av aksjer, verdipapirer og andre finansielle instrumenter, fungerende som holdingselskap, samt det som naturlig er forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 97,000
Est. value
NOK 267,000

Financial health · 2025

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

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

Who owns IVNETSERIGNER AS?

MAGNUS JOHAN MØRK
IVNETSERIGNER AS
NOK 0 rev. · NOK −5,000 profit

IVNETSERIGNER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IVNETSERIGNER AS own?

IVNETSERIGNER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about IVNETSERIGNER AS

Who owns IVNETSERIGNER AS?

MAGNUS JOHAN MØRK is the largest registered owner, with 100.0%.

What is the revenue of IVNETSERIGNER AS?

IVNETSERIGNER AS had revenue of NOK 0 in 2025.

Where is IVNETSERIGNER AS based?

IVNETSERIGNER AS has its business address in Oslo.

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

Report a problem

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