biztrac. BETA
COMPANY REGISTER PROFILE
935727189 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Office administrative and support activities

NAVITAS PETROLEUM NOK FINCO AS

Org. no. 935727189 Limited company (AS) Asker Incorporated 2025 Active
Operating profit NOK −164,000
Equity NOK −134,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−134k kr).

NAVITAS PETROLEUM NOK FINCO AS is registered as a limited company in Asker, Akershus with organisation number 935727189. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Særskilt finansiell enhet for konsernet det er en del av, hvis formål er utstedelse av obligasjoner og øvrige sertifikater og for påfølgende administrering av nevnte obligasjoner og øvrige sertifikater.”.

Former names: NFH 250655 AS

Key figures · 2025

Operating profit
NOK −164,000
Equity
NOK −134,000

Financial health · 2025

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

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

Who owns NAVITAS PETROLEUM NOK FINCO AS?

NAVITAS PETROLEUM LP IL
NAVITAS PETROLEUM NOK FINCO AS
· NOK −164,000 profit

NAVITAS PETROLEUM NOK FINCO AS has 1 registered shareholder:

  • NAVITAS PETROLEUM LP 100.0%
All shareholders and roles →

Frequently asked questions about NAVITAS PETROLEUM NOK FINCO AS

Who owns NAVITAS PETROLEUM NOK FINCO AS?

NAVITAS PETROLEUM LP is the largest registered owner, with 100.0%.

Where is NAVITAS PETROLEUM NOK FINCO AS based?

NAVITAS PETROLEUM NOK FINCO AS has its business address in Asker.

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.