biztrac. BETA
COMPANY REGISTER PROFILE
931025120 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Freight ocean transport

NFH FBM 230301 AS

Org. no. 931025120 Limited company (AS) Oslo Incorporated 2023 Active
Revenue 2025 NOK 37.8m
Operating profit NOK −22.7m
Equity NOK 144.1m
Incorporated 2023
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22,7 mill kr).

NFH FBM 230301 AS is registered as a limited company in Oslo, Oslo with organisation number 931025120. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Å drive skipsfart og rederivirksomhet samt hva som hermed står i forbindelse, herunder deltagelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 37.8m in revenue and NOK −22.7m in operating profit.

Key figures · 2025

Revenue
NOK 37.8m
▼ −61 %
Operating profit
NOK −22.7m
▼ −151 %
Equity
NOK 144.1m
▼ −14 %
Est. value
NOK 88.5m

Financial health · 2025

Liquidity
9.01
Very good
Current assets ÷ current liabilities
Profitability
-13.6%
Not satisfactory
Return on total assets
Solidity
98.9%
Very good
Equity as a share of total capital

Who owns NFH FBM 230301 AS?

NFH FBM 230301 AS
NOK 37.8m rev. · NOK −22.7m profit

NFH FBM 230301 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NFH FBM 230301 AS er morselskap for 2 datterselskaper:

Frequently asked questions about NFH FBM 230301 AS

Who owns NFH FBM 230301 AS?

ATLANTICA PSV AS is the largest registered owner, with 100.0%.

What is the revenue of NFH FBM 230301 AS?

NFH FBM 230301 AS had revenue of NOK 37.8m in 2025.

Where is NFH FBM 230301 AS based?

NFH FBM 230301 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.