BIZTRAC BETA
Manufacture of soft drinks and bottled waters

SAFTSUSE AS

Org. no. 912902234 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK −218,000
Equity NOK −971,000
Incorporated 2013
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−971k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−218k kr).

SAFTSUSE AS is registered as a limited company in Bergen, Vestland with organisation number 912902234. The business is classified under manufacture of soft drinks and bottled waters (NACE 11.070). The company was incorporated in 2013. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Produksjon og salg av saft, leskedrikker, samt hva som hermed kan settes i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK −218,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK −218,000
Equity
NOK −971,000

Financial health · 2024

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAFTSUSE AS?

GRETE VATLE OSBERG
SAFTSUSE AS
NOK 8.8m rev. · NOK −218,000 profit

SAFTSUSE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAFTSUSE AS

Who owns SAFTSUSE AS?

GRETE VATLE OSBERG is the largest registered owner, with 50.0%.

What is the revenue of SAFTSUSE AS?

SAFTSUSE AS had revenue of NOK 8.8m in 2024.

Who is the general manager of SAFTSUSE AS?

Willy Rostrup Osberg is registered as general manager of SAFTSUSE AS.

Where is SAFTSUSE AS based?

SAFTSUSE AS has its business address in Arnatveit.

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.