biztrac. BETA
COMPANY REGISTER PROFILE
932758830 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of fish, crustaceans and molluscs

HUSMANN FISKEFORRETNING AS

Org. no. 932758830 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −179,000
Equity NOK −521,000
Incorporated 2023
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−521k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−179k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HUSMANN FISKEFORRETNING AS is registered as a limited company in Oslo, Oslo with organisation number 932758830. The business is classified under retail sale of fish, crustaceans and molluscs (NACE 47.230). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg og bearbeiding av næringsmidler, samt deltakelse i selskaper med samme eller lignende formål.”.

Key figures · 2025

Operating profit
NOK −179,000
▲ +49 %
Equity
NOK −521,000
▼ −114 %

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
-56.2%
Not satisfactory
Return on total assets
Solidity
-186.0%
Weak
Equity as a share of total capital

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

Who owns HUSMANN FISKEFORRETNING AS?

HUSMANN FISKEFORRETNING AS
· NOK −179,000 profit

HUSMANN FISKEFORRETNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSMANN FISKEFORRETNING AS

Who owns HUSMANN FISKEFORRETNING AS?

FRØ NORDIC AS is the largest registered owner, with 100.0%.

Where is HUSMANN FISKEFORRETNING AS based?

HUSMANN FISKEFORRETNING AS has its business address in Oslo.

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.