BIZTRAC BETA
COMPANY REGISTER PROFILE
928167585 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SANDLOKK INVEST AS

Org. no. 928167585 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −59,000
Incorporated 2021
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−59k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

SANDLOKK INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 928167585. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Investering.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK −59,000

Financial health · 2025

Liquidity
2.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17507.4%
Weak
Equity as a share of total capital

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

Who owns SANDLOKK INVEST AS?

SANDLOKK INVEST AS
NOK 0 rev. · NOK −4,000 profit

SANDLOKK INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANDLOKK INVEST AS

Who owns SANDLOKK INVEST AS?

Stian Sandløkk is the largest registered owner, with 50.0%.

What is the revenue of SANDLOKK INVEST AS?

SANDLOKK INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of SANDLOKK INVEST AS?

Stian Sandløkk is registered as general manager of SANDLOKK INVEST AS.

Where is SANDLOKK INVEST AS based?

SANDLOKK INVEST AS has its business address in Paradis.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.