biztrac. BETA
COMPANY REGISTER PROFILE
929312295 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of fish, crustaceans and molluscs

SMART SEAFOOD AS

Org. no. 929312295 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 222,000
Equity NOK 438,000
Incorporated 2022
Share capital NOK 325,000

SMART SEAFOOD AS is registered as a limited company in Bergen, Vestland with organisation number 929312295. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2022. Registered share capital is NOK 325,000, divided into 325000 shares. The company's stated purpose is: “Selge varer og tjenester innen sjømat og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 222,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▲ +4 %
Operating profit
NOK 222,000
▲ +1428 %
Equity
NOK 438,000
▲ +331 %
Est. value
NOK 778,000

Financial health · 2025

Liquidity
2.04
Very good
Current assets ÷ current liabilities
Profitability
31.0%
Very good
Return on total assets
Solidity
32.2%
Good
Equity as a share of total capital

Who owns SMART SEAFOOD AS?

SMART SEAFOOD AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMART SEAFOOD AS

Who owns SMART SEAFOOD AS?

KNOTTEN INVEST AS is the largest registered owner, with 35.0%.

What is the revenue of SMART SEAFOOD AS?

SMART SEAFOOD AS had revenue of NOK 2.5m in 2025.

Who is the general manager of SMART SEAFOOD AS?

Tord Hauge Knotten is registered as general manager of SMART SEAFOOD AS.

Where is SMART SEAFOOD AS based?

SMART SEAFOOD 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 03.10.2026.

Report a problem

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