BIZTRAC BETA
Rental and operating of own or leased real estate

FØRESVIKVEGEN 40 AS

Org. no. 933250164 Limited company (AS) Haugesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 1.7m
Equity NOK 14.0m
Incorporated 2023
Share capital NOK 1.0m

Signals

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

FØRESVIKVEGEN 40 AS is registered as a limited company in Haugesund, Rogaland with organisation number 933250164. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Utleie og utvikling av fast eiendom, herunder kjøp og salg samt alt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 1.7m
Equity
NOK 14.0m
Est. value
NOK 12.4m

Financial health · 2025

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.8%
Satisfactory
Equity as a share of total capital

Who owns FØRESVIKVEGEN 40 AS?

TERMINALS AS
FØRESVIKVEGEN 40 AS
NOK 2.7m rev. · NOK 1.7m profit

FØRESVIKVEGEN 40 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FØRESVIKVEGEN 40 AS

Who owns FØRESVIKVEGEN 40 AS?

TERMINALS AS is the largest registered owner, with 100.0%.

What is the revenue of FØRESVIKVEGEN 40 AS?

FØRESVIKVEGEN 40 AS had revenue of NOK 2.7m in 2025.

Where is FØRESVIKVEGEN 40 AS based?

FØRESVIKVEGEN 40 AS has its business address in Haugesund.

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.