BIZTRAC BETA
Wholesale of other machinery and equipment

SALARSAFE AS

Org. no. 924539062 Limited company (AS) Karmøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −854,000
Equity NOK 2.3m
Incorporated 2020
Share capital NOK 38,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−854k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SALARSAFE AS is registered as a limited company in Karmøy, Rogaland with organisation number 924539062. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2020. Registered share capital is NOK 38,000, divided into 1261712 shares. The company's stated purpose is: “Kjøp, salg og utleie av varer og tjenester til maritim sektor.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −854,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −854,000
Equity
NOK 2.3m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
84.8%
Very good
Equity as a share of total capital

Who owns SALARSAFE AS?

AQUAFARM EQUIPMENT AS
SALARSAFE AS
NOK 0 rev. · NOK −854,000 profit

SALARSAFE AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about SALARSAFE AS

Who owns SALARSAFE AS?

AQUAFARM EQUIPMENT AS is the largest registered owner, with 83.1%.

What is the revenue of SALARSAFE AS?

SALARSAFE AS had revenue of NOK 0 in 2024.

Who is the general manager of SALARSAFE AS?

Stian Milde Rennestraum is registered as general manager of SALARSAFE AS.

Where is SALARSAFE AS based?

SALARSAFE AS has its business address in Torvastad.

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.