BIZTRAC BETA
Rental and operating of own or leased real estate

BJERKE HOLDING AS

Org. no. 988948551 Limited company (AS) Lillestrøm Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 354,000
Equity NOK 41.6m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BJERKE HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 988948551. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 354,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 354,000
Equity
NOK 41.6m
Est. value
NOK 29.2m

Financial health · 2024

Liquidity
11.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.0%
Very good
Equity as a share of total capital

Who owns BJERKE HOLDING AS?

KNUT OLE BJERKE
BJERKE HOLDING AS
NOK 2.3m rev. · NOK 354,000 profit

BJERKE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJERKE HOLDING AS own?

BJERKE HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BJERKE HOLDING AS

Who owns BJERKE HOLDING AS?

KNUT OLE BJERKE is the largest registered owner, with 100.0%.

What is the revenue of BJERKE HOLDING AS?

BJERKE HOLDING AS had revenue of NOK 2.3m in 2024.

Where is BJERKE HOLDING AS based?

BJERKE HOLDING AS has its business address in Fetsund.

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.