BIZTRAC BETA
Rental and operating of own or leased real estate

SVANHOLMEN 7 AS

Org. no. 975943720 Limited company (AS) Strand Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK 2.0m
Equity NOK 2.3m
Incorporated 1995
Share capital NOK 2.0m

Signals

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

SVANHOLMEN 7 AS is registered as a limited company in Strand, Rogaland with organisation number 975943720. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Selskapets virksomhet er å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK 2.0m
Equity
NOK 2.3m
Est. value
NOK 4.6m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

Who owns SVANHOLMEN 7 AS?

ROGLOG AS
SVANHOLMEN 7 AS
NOK 5.9m rev. · NOK 2.0m profit

SVANHOLMEN 7 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVANHOLMEN 7 AS

Who owns SVANHOLMEN 7 AS?

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

What is the revenue of SVANHOLMEN 7 AS?

SVANHOLMEN 7 AS had revenue of NOK 5.9m in 2025.

Who is the general manager of SVANHOLMEN 7 AS?

Ola Soppeland is registered as general manager of SVANHOLMEN 7 AS.

Where is SVANHOLMEN 7 AS based?

SVANHOLMEN 7 AS has its business address in Tau.

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.