BIZTRAC BETA
Marine fishing

HAN RØDER AS

Org. no. 930640123 Limited company (AS) Vestvågøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 160,000
Operating profit NOK −300,000
Equity NOK 451,000
Incorporated 2022
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−300k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HAN RØDER AS is registered as a limited company in Vestvågøy, Nordland with organisation number 930640123. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2022. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investeringer i andre aksjeselskaper, eiendom, og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK −300,000 in operating profit.

Key figures · 2025

Revenue
NOK 160,000
Operating profit
NOK −300,000
Equity
NOK 451,000
Est. value
NOK 429,000

Financial health · 2025

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

Who owns HAN RØDER AS?

TEMP HOLDING AS
HAN RØDER AS
NOK 160,000 rev. · NOK −300,000 profit

HAN RØDER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HAN RØDER AS own?

HAN RØDER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAN RØDER AS

Who owns HAN RØDER AS?

TEMP HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of HAN RØDER AS?

HAN RØDER AS had revenue of NOK 160,000 in 2025.

Where is HAN RØDER AS based?

HAN RØDER AS has its business address in Ballstad.

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.