BIZTRAC BETA
Rental and operating of own or leased real estate

SOLLIVEIEN 11 AS

Org. no. 999207987 Limited company (AS) Fredrikstad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 570,000
Operating profit NOK 327,000
Equity NOK 728,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

SOLLIVEIEN 11 AS is registered as a limited company in Fredrikstad, Østfold with organisation number 999207987. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie og drive fast eiendom samt hva hermed står i forbindelse. Herunder også deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 570,000 in revenue and NOK 327,000 in operating profit.

Key figures · 2025

Revenue
NOK 570,000
Operating profit
NOK 327,000
Equity
NOK 728,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SOLLIVEIEN 11 AS?

ABM HOLDING AS
SOLLIVEIEN 11 AS
NOK 570,000 rev. · NOK 327,000 profit

SOLLIVEIEN 11 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SOLLIVEIEN 11 AS er morselskap for 2 datterselskaper:

Frequently asked questions about SOLLIVEIEN 11 AS

Who owns SOLLIVEIEN 11 AS?

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

What is the revenue of SOLLIVEIEN 11 AS?

SOLLIVEIEN 11 AS had revenue of NOK 570,000 in 2025.

Where is SOLLIVEIEN 11 AS based?

SOLLIVEIEN 11 AS has its business address in Rolvsøy.

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.