BIZTRAC BETA
Other manufacturing n.e.c.

SAFEBACK AS

Org. no. 820851242 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −1.5m
Equity NOK 12.0m
Incorporated 2018
Share capital NOK 244,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).
  • Nylig endring 2026-06-09 Aksjekapital registrert 2026-06-09.

SAFEBACK AS is registered as a limited company in Bergen, Vestland with organisation number 820851242. The business is classified under other manufacturing n.e.c. (NACE 32.990). The company was incorporated in 2018. Registered share capital is NOK 244,000, divided into 244295 shares. The company's stated purpose is: “Utvikle, prosjektere og levere produkter innen snøskredsikkerhet og til sportsindustrien/forbrukermarkedet, samt utføre tjenester og annen virksomhet som står i naturlig forhold til dette. Teknologien kan også brukes innen andre industrier hvor dette faller naturlig.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −1.5m
Equity
NOK 12.0m
Est. value
NOK 18.3m

Financial health · 2024

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

Who owns SAFEBACK AS?

SAFEBACK HOLDING AS
SAFEBACK AS
NOK 2.1m rev. · NOK −1.5m profit

SAFEBACK AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about SAFEBACK AS

Who owns SAFEBACK AS?

SAFEBACK HOLDING AS is the largest registered owner, with 39.6%.

What is the revenue of SAFEBACK AS?

SAFEBACK AS had revenue of NOK 2.1m in 2024.

Where is SAFEBACK AS based?

SAFEBACK 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.