BIZTRAC BETA
Development of building projects

STORD BOLIG AS

Org. no. 933272575 Limited company (AS) Stord Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 10.5m
Operating profit NOK 311,000
Equity NOK 1.8m
Incorporated 2024
Share capital NOK 1.8m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-27 Adresseendring registrert 2026-02-27.

STORD BOLIG AS is registered as a limited company in Stord, Vestland with organisation number 933272575. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 1.8m, divided into 1750000 shares. The company's stated purpose is: “Å eie, utvikle, forvalte og drive fast eiendom, herunder utleie og salg av bolig- og næringseiendom, samt virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.5m in revenue and NOK 311,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.5m
Operating profit
NOK 311,000
Equity
NOK 1.8m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
-38.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.7%
Satisfactory
Equity as a share of total capital

Who owns STORD BOLIG AS?

STORD EIENDOMSFORVALTNING AS
STORD BOLIG AS
NOK 10.5m rev. · NOK 311,000 profit

STORD BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORD BOLIG AS

Who owns STORD BOLIG AS?

STORD EIENDOMSFORVALTNING AS is the largest registered owner, with 100.0%.

What is the revenue of STORD BOLIG AS?

STORD BOLIG AS had revenue of NOK 10.5m in 2024.

Where is STORD BOLIG AS based?

STORD BOLIG AS has its business address in Stord.

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.