BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

BRODWALL ØRE NESE HALS AS

Org. no. 934851080 Limited company (AS) Alta Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.6m
Equity NOK 56,000
Incorporated 2024
Share capital NOK 30,000

BRODWALL ØRE NESE HALS AS is registered as a limited company in Alta, Finnmark with organisation number 934851080. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Legevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.6m
Equity
NOK 56,000
Est. value
NOK 5.2m

Financial health · 2025

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

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

Who owns BRODWALL ØRE NESE HALS AS?

BRODWALL BERGE HOLDING AS
BRODWALL ØRE NESE HALS AS
NOK 2.6m rev. · NOK 1.6m profit

BRODWALL ØRE NESE HALS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRODWALL ØRE NESE HALS AS

Who owns BRODWALL ØRE NESE HALS AS?

BRODWALL BERGE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRODWALL ØRE NESE HALS AS?

BRODWALL ØRE NESE HALS AS had revenue of NOK 2.6m in 2025.

Who is the general manager of BRODWALL ØRE NESE HALS AS?

Nicolai Brodwall Berge is registered as general manager of BRODWALL ØRE NESE HALS AS.

Where is BRODWALL ØRE NESE HALS AS based?

BRODWALL ØRE NESE HALS AS has its business address in Alta.

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.