BIZTRAC BETA
Rental and operating of own or leased real estate

BROKELANDSHEIA S11 AS

Org. no. 935097479 Limited company (AS) Gjerstad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 329,000
Operating profit NOK 226,000
Equity NOK 896,000
Incorporated 2025
Share capital NOK 950,000

BROKELANDSHEIA S11 AS is registered as a limited company in Gjerstad, Agder with organisation number 935097479. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 950,000, divided into 950000 shares. The company's stated purpose is: “Eie, drifte og leie ut fast eiendom og eiendomsutvikling generelt. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 329,000 in revenue and NOK 226,000 in operating profit.

Key figures · 2025

Revenue
NOK 329,000
Operating profit
NOK 226,000
Equity
NOK 896,000
Est. value
NOK 952,000

Financial health · 2025

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

Who owns BROKELANDSHEIA S11 AS?

BROKELANDSHEIA 20 AS
BROKELANDSHEIA S11 AS
NOK 329,000 rev. · NOK 226,000 profit

BROKELANDSHEIA S11 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BROKELANDSHEIA S11 AS

Who owns BROKELANDSHEIA S11 AS?

BROKELANDSHEIA 20 AS is the largest registered owner, with 50.0%.

What is the revenue of BROKELANDSHEIA S11 AS?

BROKELANDSHEIA S11 AS had revenue of NOK 329,000 in 2025.

Who is the general manager of BROKELANDSHEIA S11 AS?

Cato Solstad is registered as general manager of BROKELANDSHEIA S11 AS.

Where is BROKELANDSHEIA S11 AS based?

BROKELANDSHEIA S11 AS has its business address in Sundebru.

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.