BIZTRAC BETA
Rental and operating of own or leased real estate

BRAKA EIENDOM AS

Org. no. 932754827 Limited company (AS) Nord-Fron Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 351,000
Equity NOK 33,000
Incorporated 2023
Share capital NOK 30,000

BRAKA EIENDOM AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 932754827. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg, restaurering, oppføring av eiendom, utleie av fast eiendom, samt det som naturlig står i forbindelse med dette og eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 351,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 351,000
Equity
NOK 33,000
Est. value
NOK 529,000

Financial health · 2024

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

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

Who owns BRAKA EIENDOM AS?

BRAKA INVEST AS
BRAKA EIENDOM AS
NOK 1.5m rev. · NOK 351,000 profit

BRAKA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRAKA EIENDOM AS

Who owns BRAKA EIENDOM AS?

BRAKA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BRAKA EIENDOM AS?

BRAKA EIENDOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of BRAKA EIENDOM AS?

Pål Gunnar Brandvold is registered as general manager of BRAKA EIENDOM AS.

Where is BRAKA EIENDOM AS based?

BRAKA EIENDOM AS has its business address in Vinstra.

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.