biztrac. BETA
COMPANY REGISTER PROFILE
920765173 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

NAVIGO HOLDING AS

Org. no. 920765173 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 4.3m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).
  • Nylig endring 2026-06-25 Adresseendring registrert 2026-06-25.

NAVIGO HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 920765173. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, andeler og fast eiendom, samt virksomhet som har tilknytning til disse. Selskapet skal drive med konsulentvirksomhet og skal ta del i andre selskap.”.

Key figures · 2025

Operating profit
NOK −19,000
▼ −81 %
Equity
NOK 4.3m
▲ +50 %
Est. value
NOK 11.8m

Financial health · 2025

Liquidity
160.88
Very good
Current assets ÷ current liabilities
Profitability
40.3%
Very good
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns NAVIGO HOLDING AS?

NAVIGO HOLDING AS
· NOK −19,000 profit

NAVIGO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NAVIGO HOLDING AS own?

NAVIGO HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about NAVIGO HOLDING AS

Who owns NAVIGO HOLDING AS?

Andreas Olsen Tinglum is the largest registered owner, with 100.0%.

Who is the general manager of NAVIGO HOLDING AS?

Andreas Olsen Tinglum is registered as general manager of NAVIGO HOLDING AS.

Where is NAVIGO HOLDING AS based?

NAVIGO HOLDING 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 03.10.2026.

Report a problem

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