BIZTRAC BETA
Rental and operating of own or leased real estate

BARSTØLVEIEN 40 AS

Org. no. 991896465 Limited company (AS) Kristiansand Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 4.3m
Equity NOK 647,000
Incorporated 2007
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.

BARSTØLVEIEN 40 AS is registered as a limited company in Kristiansand, Agder with organisation number 991896465. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie og drifte eiendommen Barstølveien 40 og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 4.3m
Equity
NOK 647,000
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns BARSTØLVEIEN 40 AS?

FRØYSAA HOLDING AS
BARSTØLVEIEN 40 AS
NOK 5.0m rev. · NOK 4.3m profit

BARSTØLVEIEN 40 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BARSTØLVEIEN 40 AS er morselskap for 5 datterselskaper:

Frequently asked questions about BARSTØLVEIEN 40 AS

Who owns BARSTØLVEIEN 40 AS?

FRØYSAA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BARSTØLVEIEN 40 AS?

BARSTØLVEIEN 40 AS had revenue of NOK 5.0m in 2024.

Where is BARSTØLVEIEN 40 AS based?

BARSTØLVEIEN 40 AS has its business address in Kristiansand S.

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.