biztrac. BETA
COMPANY REGISTER PROFILE
932300397 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BAR BAKKE EIENDOM AS

Org. no. 932300397 Limited company (AS) Surnadal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 523,000
Operating profit NOK 268,000
Equity NOK 758,000
Incorporated 2023
Share capital NOK 70,000

BAR BAKKE EIENDOM AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 932300397. 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 70,000, divided into 70 shares. The company's stated purpose is: “Utleie til næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 523,000 in revenue and NOK 268,000 in operating profit.

Key figures · 2025

Revenue
NOK 523,000
▼ −5 %
Operating profit
NOK 268,000
▼ −11 %
Equity
NOK 758,000
▲ +5 %
Est. value
NOK 934,000

Financial health · 2025

Liquidity
2.11
Very good
Current assets ÷ current liabilities
Profitability
6.7%
Satisfactory
Return on total assets
Solidity
19.4%
Good
Equity as a share of total capital

Who owns BAR BAKKE EIENDOM AS?

BAR BAKKE EIENDOM AS
NOK 523,000 rev. · NOK 268,000 profit

BAR BAKKE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BAR BAKKE EIENDOM AS own?

BAR BAKKE EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BAR BAKKE EIENDOM AS

Who owns BAR BAKKE EIENDOM AS?

Ingebrigt Gjerstad is the largest registered owner, with 50.0%.

What is the revenue of BAR BAKKE EIENDOM AS?

BAR BAKKE EIENDOM AS had revenue of NOK 523,000 in 2025.

Where is BAR BAKKE EIENDOM AS based?

BAR BAKKE EIENDOM AS has its business address in Surnadal.

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.