BIZTRAC BETA
Uoppgitt

KEVIN BERGHAGEN AS

Org. no. 934223608 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KEVIN BERGHAGEN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 934223608. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2024

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 KEVIN BERGHAGEN AS?

KEVIN GULLIKSEN BERGHAGEN
KEVIN BERGHAGEN AS
· NOK −1,000 profit

KEVIN BERGHAGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KEVIN BERGHAGEN AS own?

KEVIN BERGHAGEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KEVIN BERGHAGEN AS

Who owns KEVIN BERGHAGEN AS?

KEVIN GULLIKSEN BERGHAGEN is the largest registered owner, with 100.0%.

Who is the general manager of KEVIN BERGHAGEN AS?

Kevin Gulliksen Berghagen is registered as general manager of KEVIN BERGHAGEN AS.

Where is KEVIN BERGHAGEN AS based?

KEVIN BERGHAGEN AS has its business address in Lillestrøm.

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.