biztrac. BETA
COMPANY REGISTER PROFILE
922142629 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

BJØRN HARBO AS

Org. no. 922142629 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 2.5m
Operating profit NOK 1.4m
Equity NOK 1.2m
Incorporated 2018
Share capital NOK 30,000

BJØRN HARBO AS is registered as a limited company in Oslo, Oslo with organisation number 922142629. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Legevirksomhet. Videre kjøp/salg og drift av fast eiendom, kjøp/salg av aksjer og andre verdipapirer og hva som står i forbindelse med dette. Produksjon og salg av møbler og andre produkter knyttet til snekkervirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▲ +13 %
Operating profit
NOK 1.4m
▲ +36 %
Equity
NOK 1.2m
▲ +3758 %
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
3.21
Very good
Current assets ÷ current liabilities
Profitability
49.6%
Very good
Return on total assets
Solidity
36.6%
Good
Equity as a share of total capital

Who owns BJØRN HARBO AS?

BJØRN HARBO AS
NOK 2.5m rev. · NOK 1.4m profit

BJØRN HARBO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRN HARBO AS

Who owns BJØRN HARBO AS?

Bjørn Harbo is the largest registered owner, with 100.0%.

What is the revenue of BJØRN HARBO AS?

BJØRN HARBO AS had revenue of NOK 2.5m in 2025.

Who is the general manager of BJØRN HARBO AS?

Bjørn Harbo is registered as general manager of BJØRN HARBO AS.

Where is BJØRN HARBO AS based?

BJØRN HARBO AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.