biztrac. BETA
COMPANY REGISTER PROFILE
935448433 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Raising of other poultry

BRUDHEIM DRESSUR AS

Org. no. 935448433 Limited company (AS) Nesodden Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 873,000
Operating profit NOK 194,000
Equity NOK 356,000
Incorporated 2025
Share capital NOK 30,000

BRUDHEIM DRESSUR AS is registered as a limited company in Nesodden, Akershus with organisation number 935448433. The business is classified under raising of other poultry (NACE 01.479). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppstalling av hester, trening av hest, salg av hest og undervisning av hest og rytter.”. The most recent filed accounts, for the 2025 financial year, show NOK 873,000 in revenue and NOK 194,000 in operating profit.

Key figures · 2025

Revenue
NOK 873,000
Operating profit
NOK 194,000
Equity
NOK 356,000
Est. value
NOK 710,000

Financial health · 2025

Liquidity
3.19
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
74.1%
Very good
Equity as a share of total capital

Who owns BRUDHEIM DRESSUR AS?

BRUDHEIM DRESSUR AS
NOK 873,000 rev. · NOK 194,000 profit

BRUDHEIM DRESSUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRUDHEIM DRESSUR AS

Who owns BRUDHEIM DRESSUR AS?

Thea Constanse Wang Brudheim is the largest registered owner, with 100.0%.

What is the revenue of BRUDHEIM DRESSUR AS?

BRUDHEIM DRESSUR AS had revenue of NOK 873,000 in 2025.

Who is the general manager of BRUDHEIM DRESSUR AS?

Thea Constanse Wang Brudheim is registered as general manager of BRUDHEIM DRESSUR AS.

Where is BRUDHEIM DRESSUR AS based?

BRUDHEIM DRESSUR AS has its business address in Nesodden.

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.