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

KROGDAHL HOLDING AS

Org. no. 931125273 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −8,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KROGDAHL HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931125273. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer.”.

Key figures · 2025

Operating profit
NOK −8,000
▲ +47 %

Financial health · 2025

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

Who owns KROGDAHL HOLDING AS?

KROGDAHL HOLDING AS
· NOK −8,000 profit

KROGDAHL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KROGDAHL HOLDING AS own?

KROGDAHL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KROGDAHL HOLDING AS

Who owns KROGDAHL HOLDING AS?

NICOLAI BJERKE KROGDAHL is the largest registered owner, with 100.0%.

Where is KROGDAHL HOLDING AS based?

KROGDAHL HOLDING AS has its business address in Oslo.

Property

Business address Lybekkveien 9F, 0772 Oslo
Cadastral unit 301-27/420/0/0
Building Tomannsbolig, vertikal · 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.