biztrac. BETA
COMPANY REGISTER PROFILE
921095414 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

KEYTOR MARITIME PARTNER AS

Org. no. 921095414 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK −118,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

KEYTOR MARITIME PARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 921095414. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kapitalforvaltning, samt det som naturlig står i forbindelse med dette.”.

Former names: ELEMENT IRON AS, ELEMENT DIGITAL VENTURES AS, DLTX VENTURES AS, RISØR PROSJEKT AS

Key figures · 2025

Operating profit
NOK −21,000
▲ +42 %
Equity
NOK −118,000
▼ −22 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns KEYTOR MARITIME PARTNER AS?

KEYTOR MARITIME PARTNER AS
· NOK −21,000 profit

KEYTOR MARITIME PARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KEYTOR MARITIME PARTNER AS

Who owns KEYTOR MARITIME PARTNER AS?

Edward Michael Ortiz Lien is the largest registered owner, with 100.0%.

Where is KEYTOR MARITIME PARTNER AS based?

KEYTOR MARITIME PARTNER 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.