BIZTRAC BETA
Uoppgitt

SMRTFISK HOLDING AS

Org. no. 934361016 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

SMRTFISK HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 934361016. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns SMRTFISK HOLDING AS?

AUDUN SMØRGRAV
SMRTFISK HOLDING AS
· NOK −6,000 profit

SMRTFISK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMRTFISK HOLDING AS own?

SMRTFISK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMRTFISK HOLDING AS

Who owns SMRTFISK HOLDING AS?

AUDUN SMØRGRAV is the largest registered owner, with 100.0%.

Who is the general manager of SMRTFISK HOLDING AS?

Audun Smørgrav is registered as general manager of SMRTFISK HOLDING AS.

Where is SMRTFISK HOLDING AS based?

SMRTFISK HOLDING AS has its business address in Drammen.

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.