BIZTRAC BETA
Marine fishing

NIMROD BODØ AS

Org. no. 991482601 Limited company (AS) Askøy Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 352,000
Operating profit NOK −576,000
Equity NOK −756,000
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−756k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−576k kr).

NIMROD BODØ AS is registered as a limited company in Askøy, Vestland with organisation number 991482601. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Fiske, fangst og oppføring og vedlikehold av bygninger med tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 352,000 in revenue and NOK −576,000 in operating profit.

Key figures · 2025

Revenue
NOK 352,000
Operating profit
NOK −576,000
Equity
NOK −756,000

Financial health · 2025

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

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

Who owns NIMROD BODØ AS?

HELGE HARRY NYMO
NIMROD BODØ AS
NOK 352,000 rev. · NOK −576,000 profit

NIMROD BODØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIMROD BODØ AS

Who owns NIMROD BODØ AS?

HELGE HARRY NYMO is the largest registered owner, with 100.0%.

What is the revenue of NIMROD BODØ AS?

NIMROD BODØ AS had revenue of NOK 352,000 in 2025.

Who is the general manager of NIMROD BODØ AS?

Odin Varg Jørgensen is registered as general manager of NIMROD BODØ AS.

Where is NIMROD BODØ AS based?

NIMROD BODØ AS has its business address in Strusshamn.

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.