BIZTRAC BETA
Rental and operating of own or leased real estate

SALTRØDSENTERET AS

Org. no. 988088102 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 6.5m
Operating profit NOK 2.8m
Equity NOK 17.7m
Incorporated 2005
Share capital NOK 5.0m

Signals

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

SALTRØDSENTERET AS is registered as a limited company in Bergen, Vestland with organisation number 988088102. 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 5.0m, divided into 3 shares. The company's stated purpose is: “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 2024 financial year, show NOK 6.5m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 6.5m
Operating profit
NOK 2.8m
Equity
NOK 17.7m
Est. value
NOK 16.5m

Financial health · 2024

Liquidity
5.17
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.3%
Good
Equity as a share of total capital

Who owns SALTRØDSENTERET AS?

SANDVIKEN EIENDOMSUTVIKLING AS
SALTRØDSENTERET AS
NOK 6.5m rev. · NOK 2.8m profit

SALTRØDSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SALTRØDSENTERET AS er morselskap for 20 datterselskaper:

Frequently asked questions about SALTRØDSENTERET AS

Who owns SALTRØDSENTERET AS?

SANDVIKEN EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of SALTRØDSENTERET AS?

SALTRØDSENTERET AS had revenue of NOK 6.5m in 2024.

Where is SALTRØDSENTERET AS based?

SALTRØDSENTERET AS has its business address in Bergen.

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.