BIZTRAC BETA
Development of building projects

VESTLANDET UTVIKLING AS

Org. no. 920235786 Limited company (AS) Sunnfjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 16.1m
Operating profit NOK 1.1m
Equity NOK 12.2m
Incorporated 2017
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VESTLANDET UTVIKLING AS is registered as a limited company in Sunnfjord, Vestland with organisation number 920235786. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i, utvikling, oppføring og salg av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 16.1m
Operating profit
NOK 1.1m
Equity
NOK 12.2m
Est. value
NOK 10.3m

Financial health · 2025

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

Who owns VESTLANDET UTVIKLING AS?

ULLALAND BYGG OG EIGEDOMSUTVIKLING AS
VESTLANDET UTVIKLING AS
NOK 16.1m rev. · NOK 1.1m profit

VESTLANDET UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VESTLANDET UTVIKLING AS

Who owns VESTLANDET UTVIKLING AS?

ULLALAND BYGG OG EIGEDOMSUTVIKLING AS is the largest registered owner, with 51.0%.

What is the revenue of VESTLANDET UTVIKLING AS?

VESTLANDET UTVIKLING AS had revenue of NOK 16.1m in 2025.

Where is VESTLANDET UTVIKLING AS based?

VESTLANDET UTVIKLING AS has its business address in Førde.

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.