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

VESTLAND EIENDOM AS

Org. no. 988031186 Limited company (AS) Bamble Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −40,000
Equity NOK 14.7m
Incorporated 2005
Share capital NOK 190,000

Signals

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

VESTLAND EIENDOM AS is registered as a limited company in Bamble, Telemark with organisation number 988031186. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 190,000, divided into 19 shares. The company's stated purpose is: “Å eie aksjer i andre selskap, investere i aksjer, andre verdipapirer og fast eiendom samt virksomhet som naturlig faller innunder dette.”.

Key figures · 2025

Operating profit
NOK −40,000
▼ −111 %
Equity
NOK 14.7m
▲ +5 %
Est. value
NOK 11.4m

Financial health · 2025

Liquidity
115.55
Very good
Current assets ÷ current liabilities
Profitability
5.3%
Weak
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns VESTLAND EIENDOM AS?

VESTLAND EIENDOM AS
· NOK −40,000 profit

VESTLAND EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VESTLAND EIENDOM AS own?

VESTLAND EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VESTLAND EIENDOM AS

Who owns VESTLAND EIENDOM AS?

Per Ragnar Vestland is the largest registered owner, with 52.6%.

Who is the general manager of VESTLAND EIENDOM AS?

Per Ragnar Vestland is registered as general manager of VESTLAND EIENDOM AS.

Where is VESTLAND EIENDOM AS based?

VESTLAND EIENDOM AS has its business address in Stathelle.

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.