biztrac. BETA
COMPANY REGISTER PROFILE
828931652 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Operation of freshwater hatcheries

RØSKESTAD SMOLT AS

Org. no. 828931652 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 69,000
Incorporated 2022
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).
  • Nylig endring 2026-09-18 Aksjekapital registrert 2026-09-18.

RØSKESTAD SMOLT AS is registered as a limited company in Asker, Akershus with organisation number 828931652. The business is classified under operation of freshwater hatcheries (NACE 03.222). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 500000 shares. The company's stated purpose is: “Produksjon, utvikling og salg av yngel, settefisk og smolt.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
▼ −143 %
Equity
NOK 69,000
▼ −16 %
Est. value
NOK 66,000

Financial health · 2025

Liquidity
20.50
Very good
Current assets ÷ current liabilities
Profitability
-17.5%
Not satisfactory
Return on total assets
Solidity
98.1%
Weak
Equity as a share of total capital

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

Who owns RØSKESTAD SMOLT AS?

RØSKESTAD SMOLT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØSKESTAD SMOLT AS

Who owns RØSKESTAD SMOLT AS?

Marit Pettersen Høkedal is the largest registered owner, with 25.0%.

What is the revenue of RØSKESTAD SMOLT AS?

RØSKESTAD SMOLT AS had revenue of NOK 0 in 2025.

Where is RØSKESTAD SMOLT AS based?

RØSKESTAD SMOLT AS has its business address in Sætre.

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.