BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

SMESTADBARNELEGENE AS

Org. no. 882793222 Limited company (AS) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 8,000
Equity NOK 264,000
Incorporated 2000
Share capital NOK 102,000

SMESTADBARNELEGENE AS is registered as a limited company in Oslo, Oslo with organisation number 882793222. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2000. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Drift av helsetjenester, investeringer i fast eiendom, inn og utland, finansplasseringer, samt annen virksomhet som naturlig hører inn under det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 8,000
Equity
NOK 264,000
Est. value
NOK 206,000

Financial health · 2024

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.7%
Good
Equity as a share of total capital

Who owns SMESTADBARNELEGENE AS?

EIRIK HERLAND
SMESTADBARNELEGENE AS
NOK 4.5m rev. · NOK 8,000 profit

SMESTADBARNELEGENE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMESTADBARNELEGENE AS

Who owns SMESTADBARNELEGENE AS?

EIRIK HERLAND is the largest registered owner, with 33.3%.

What is the revenue of SMESTADBARNELEGENE AS?

SMESTADBARNELEGENE AS had revenue of NOK 4.5m in 2024.

Who is the general manager of SMESTADBARNELEGENE AS?

Eirik Herland is registered as general manager of SMESTADBARNELEGENE AS.

Where is SMESTADBARNELEGENE AS based?

SMESTADBARNELEGENE 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 15.06.2026.

Report a problem

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