BIZTRAC BETA
Uoppgitt

EGO TIBI AS

Org. no. 926054384 Limited company (AS) Kongsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 170,000
Incorporated 2020
Share capital NOK 100,000

Signals

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

EGO TIBI AS is registered as a limited company in Kongsberg, Buskerud with organisation number 926054384. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i eiendeler og i andre selskap, derav kjøp og salg av aksjer, rådgivning, og andre produkter og tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 170,000
Est. value
NOK 200,000

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.5%
Satisfactory
Equity as a share of total capital

Who owns EGO TIBI AS?

CECILIE SØVIK
EGO TIBI AS
NOK 0 rev. · NOK −14,000 profit

EGO TIBI AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EGO TIBI AS own?

EGO TIBI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EGO TIBI AS

Who owns EGO TIBI AS?

CECILIE SØVIK is the largest registered owner, with 50.0%.

What is the revenue of EGO TIBI AS?

EGO TIBI AS had revenue of NOK 0 in 2025.

Who is the general manager of EGO TIBI AS?

Lasse Bjørkhaug is registered as general manager of EGO TIBI AS.

Where is EGO TIBI AS based?

EGO TIBI AS has its business address in Kongsberg.

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.