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

BIRCHFARM CAPITAL AS

Org. no. 927386453 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 272,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

BIRCHFARM CAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 927386453. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Forvaltning og investering av kapital.”.

Key figures · 2025

Operating profit
NOK −18,000
▼ −31 %
Equity
NOK 272,000
▲ +11 %
Est. value
NOK 314,000

Financial health · 2025

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
4.3%
Weak
Return on total assets
Solidity
41.2%
Very good
Equity as a share of total capital

Who owns BIRCHFARM CAPITAL AS?

BIRCHFARM CAPITAL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIRCHFARM CAPITAL AS

Who owns BIRCHFARM CAPITAL AS?

HAAKON BJERREGAARD MOE is the largest registered owner, with 33.3%.

Where is BIRCHFARM CAPITAL AS based?

BIRCHFARM CAPITAL AS has its business address in Oslo.

Property

Business address C/O Petter Bjerregaard Gustavsen Kirkeveien 78C, 0364 Oslo
Cadastral unit 301-46/18/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 16 units

4 companies are registered at this address.

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.