BIZTRAC BETA
COMPANY REGISTER PROFILE
930791687 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

SKEIESTØA BOLIGTUN AS

Org. no. 930791687 Limited company (AS) Bjørnafjorden Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 1.8m
Incorporated 2022
Share capital NOK 1.8m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

SKEIESTØA BOLIGTUN AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 930791687. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 1.8m, divided into 18000 shares. The company's stated purpose is: “Utvikling og salg av boligtomt.”.

Key figures · 2025

Operating profit
NOK −5,000
▼ −4 %
Equity
NOK 1.8m
▲ +0 %
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns SKEIESTØA BOLIGTUN AS?

SKEIESTØA BOLIGTUN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKEIESTØA BOLIGTUN AS

Who owns SKEIESTØA BOLIGTUN AS?

BBBOLIG EIENDOMSUTVIKLING AS is the largest registered owner, with 50.0%.

Where is SKEIESTØA BOLIGTUN AS based?

SKEIESTØA BOLIGTUN AS has its business address in Os.

Property

Business address Ulvenvegen 32, 5210 Os
Cadastral unit 4624-54/235/0/0
Building Annen industribygning · 1 unit

8 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.