BIZTRAC BETA
Rental and operating of own or leased real estate

SLUSH AS

Org. no. 931858394 Limited company (AS) Narvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 111,000
Operating profit NOK 71,000
Equity NOK 81,000
Incorporated 2023
Share capital NOK 60,000

SLUSH AS is registered as a limited company in Narvik, Nordland with organisation number 931858394. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 150 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom og flyttbar eiendom herunder kjøretøy/tilhenger, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 111,000 in revenue and NOK 71,000 in operating profit.

Key figures · 2024

Revenue
NOK 111,000
Operating profit
NOK 71,000
Equity
NOK 81,000
Est. value
NOK 161,000

Financial health · 2024

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

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

Who owns SLUSH AS?

SNAJDDER AS
SLUSH AS
NOK 111,000 rev. · NOK 71,000 profit

SLUSH AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SLUSH AS own?

SLUSH AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SLUSH AS

Who owns SLUSH AS?

SNAJDDER AS is the largest registered owner, with 25.0%.

What is the revenue of SLUSH AS?

SLUSH AS had revenue of NOK 111,000 in 2024.

Who is the general manager of SLUSH AS?

Frank Jensen is registered as general manager of SLUSH AS.

Where is SLUSH AS based?

SLUSH AS has its business address in Narvik.

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.