BIZTRAC BETA
Rental and operating of own or leased real estate

GISMERØYVEIEN 200 AS

Org. no. 923444440 Limited company (AS) Lindesnes Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 783,000
Equity NOK 1.6m
Incorporated 2019
Share capital NOK 30,000

GISMERØYVEIEN 200 AS is registered as a limited company in Lindesnes, Agder with organisation number 923444440. 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 30,000, divided into 30 shares. The company's stated purpose is: “Erverv og drift av eiendom samt alt hva dermed står i forbindelse, herunder investering i aksjer eller på annen måte delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 783,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 783,000
Equity
NOK 1.6m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
10.41
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.3%
Satisfactory
Equity as a share of total capital

Who owns GISMERØYVEIEN 200 AS?

BRØDRENE HELLE HOLDING AS
GISMERØYVEIEN 200 AS
NOK 1.5m rev. · NOK 783,000 profit

GISMERØYVEIEN 200 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GISMERØYVEIEN 200 AS

Who owns GISMERØYVEIEN 200 AS?

BRØDRENE HELLE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GISMERØYVEIEN 200 AS?

GISMERØYVEIEN 200 AS had revenue of NOK 1.5m in 2025.

Who is the general manager of GISMERØYVEIEN 200 AS?

Odd Helle is registered as general manager of GISMERØYVEIEN 200 AS.

Where is GISMERØYVEIEN 200 AS based?

GISMERØYVEIEN 200 AS has its business address in Mandal.

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.