BIZTRAC BETA
COMPANY REGISTER PROFILE
996813436 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

VERNIR AS

Org. no. 996813436 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 20,000
Incorporated 2011
Share capital NOK 160,000

Signals

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

VERNIR AS is registered as a limited company in Oslo, Oslo with organisation number 996813436. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2011. Registered share capital is NOK 160,000, divided into 160 shares. The company's stated purpose is: “Handel, utvikling, kjøp, salg og utleie av fast eiendom samt annen virksomhet som naturlig faller inn under dette ved aksjekjøp eller på annen måte.”.

Key figures · 2025

Operating profit
NOK −14,000
▲ +14 %
Equity
NOK 20,000
▼ −42 %
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns VERNIR AS?

VERNIR AS
· NOK −14,000 profit

VERNIR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VERNIR AS

Who owns VERNIR AS?

HARALD GUNNAR JODALEN is the largest registered owner, with 100.0%.

Where is VERNIR AS based?

VERNIR AS has its business address in Oslo.

Property

Business address Ekebergveien 224B, 1162 Oslo
Cadastral unit 301-183/281/0/0
Building Enebolig · 1 unit

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.