biztrac. BETA
COMPANY REGISTER PROFILE
931199455 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of construction and civil engineering machinery and equipment

OSLO LIFTHAVN AS

Org. no. 931199455 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2
Equity NOK 23,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2 kr).

OSLO LIFTHAVN AS is registered as a limited company in Oslo, Oslo with organisation number 931199455. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie/formidling av lifter og anleggsmaskiner i Oslo og omegn.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2
▲ +100 %
Equity
NOK 23,000
▼ −0 %
Est. value
NOK 33,000

Financial health · 2025

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

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

Who owns OSLO LIFTHAVN AS?

OSLO LIFTHAVN AS
NOK 0 rev. · NOK −2 profit

OSLO LIFTHAVN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO LIFTHAVN AS

Who owns OSLO LIFTHAVN AS?

Lars Christoffer Fjelltveit is the largest registered owner, with 100.0%.

What is the revenue of OSLO LIFTHAVN AS?

OSLO LIFTHAVN AS had revenue of NOK 0 in 2025.

Where is OSLO LIFTHAVN AS based?

OSLO LIFTHAVN 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.