BIZTRAC BETA
Rental and operating of own or leased real estate

SVELVIK NÆRSENTER AS

Org. no. 988349674 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK −2.0m
Equity NOK 4.3m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).

SVELVIK NÆRSENTER AS is registered as a limited company in Bærum, Akershus with organisation number 988349674. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling, drift og salg av fast eiendom og det som står i forbindelse med det, herunder å delta i andre selskaper med slikt formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK −2.0m
Equity
NOK 4.3m
Est. value
NOK 6.7m

Financial health · 2024

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.7%
Good
Equity as a share of total capital

Who owns SVELVIK NÆRSENTER AS?

SVELVIK INVEST AS
SVELVIK NÆRSENTER AS
NOK 3.1m rev. · NOK −2.0m profit

SVELVIK NÆRSENTER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SVELVIK NÆRSENTER AS er morselskap for 1 datterselskap:

Frequently asked questions about SVELVIK NÆRSENTER AS

Who owns SVELVIK NÆRSENTER AS?

SVELVIK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SVELVIK NÆRSENTER AS?

SVELVIK NÆRSENTER AS had revenue of NOK 3.1m in 2025.

Where is SVELVIK NÆRSENTER AS based?

SVELVIK NÆRSENTER AS has its business address in Jar.

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.