BIZTRAC BETA
General medical practice activities

STIAN HALSE AS

Org. no. 829631652 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK 2.4m
Equity NOK 31,000
Incorporated 2022
Share capital NOK 30,000

STIAN HALSE AS is registered as a limited company in Oslo, Oslo with organisation number 829631652. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Legetjenester. Eierskap, kjøp og salg av aksjer og aktiviteter som hører inn under det. Kjøp og salg av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 7.9m
Operating profit
NOK 2.4m
Equity
NOK 31,000
Est. value
NOK 7.7m

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STIAN HALSE AS?

STIAN EGSET HALSE
STIAN HALSE AS
NOK 7.9m rev. · NOK 2.4m profit

STIAN HALSE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STIAN HALSE AS own?

STIAN HALSE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STIAN HALSE AS

Who owns STIAN HALSE AS?

STIAN EGSET HALSE is the largest registered owner, with 100.0%.

What is the revenue of STIAN HALSE AS?

STIAN HALSE AS had revenue of NOK 7.9m in 2025.

Who is the general manager of STIAN HALSE AS?

Stian Egset Halse is registered as general manager of STIAN HALSE AS.

Where is STIAN HALSE AS based?

STIAN HALSE 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.