BIZTRAC BETA
Rental and operating of own or leased real estate

VESTRE FRIVOLD AS

Org. no. 823994192 Limited company (AS) Grimstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 38,000
Operating profit NOK −100,000
Equity NOK 718,000
Incorporated 2019
Share capital NOK 250,000

Signals

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

VESTRE FRIVOLD AS is registered as a limited company in Grimstad, Agder with organisation number 823994192. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom og hva som naturlig hører til dette. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 38,000 in revenue and NOK −100,000 in operating profit.

Key figures · 2025

Revenue
NOK 38,000
Operating profit
NOK −100,000
Equity
NOK 718,000
Est. value
NOK 655,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.4%
Good
Equity as a share of total capital

Who owns VESTRE FRIVOLD AS?

BJARNASTEIN HOLDING AS
VESTRE FRIVOLD AS
NOK 38,000 rev. · NOK −100,000 profit

VESTRE FRIVOLD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VESTRE FRIVOLD AS er morselskap for 1 datterselskap:

Frequently asked questions about VESTRE FRIVOLD AS

Who owns VESTRE FRIVOLD AS?

BJARNASTEIN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VESTRE FRIVOLD AS?

VESTRE FRIVOLD AS had revenue of NOK 38,000 in 2025.

Where is VESTRE FRIVOLD AS based?

VESTRE FRIVOLD AS has its business address in Grimstad.

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.