BIZTRAC BETA
Rental and leasing of water transport equipment

MEDTANK AS

Org. no. 923062300 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 18.2m
Operating profit NOK 16.9m
Equity NOK −41,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−41k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MEDTANK AS is registered as a limited company in Oslo, Oslo with organisation number 923062300. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive skipsfart med egne og innleide skip samt hva hermed står i forbindelse, samt deltagelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.2m in revenue and NOK 16.9m in operating profit.

Key figures · 2024

Revenue
NOK 18.2m
Operating profit
NOK 16.9m
Equity
NOK −41,000
Est. value
NOK 35.0m

Financial health · 2024

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.0%
Weak
Equity as a share of total capital

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

Who owns MEDTANK AS?

MARITIME YIELD COMPANY AS
MEDTANK AS
NOK 18.2m rev. · NOK 16.9m profit

MEDTANK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEDTANK AS

Who owns MEDTANK AS?

MARITIME YIELD COMPANY AS is the largest registered owner, with 100.0%.

What is the revenue of MEDTANK AS?

MEDTANK AS had revenue of NOK 18.2m in 2024.

Where is MEDTANK AS based?

MEDTANK 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.