BIZTRAC BETA
Rental and operating of own or leased real estate

TVETENVEIEN 152 MEVLANA 2 AS

Org. no. 932573474 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 340,000
Operating profit NOK 295,000
Equity NOK 1.4m
Incorporated 2023
Share capital NOK 239,000

TVETENVEIEN 152 MEVLANA 2 AS is registered as a limited company in Oslo, Oslo with organisation number 932573474. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 239,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, kjøp og salg av verdipapirer, samt alt hva hermed står i forbindelse, herunder å delta i andre selskaper med samme eller lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 340,000 in revenue and NOK 295,000 in operating profit.

Key figures · 2024

Revenue
NOK 340,000
Operating profit
NOK 295,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
2.81
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
91.3%
Very good
Equity as a share of total capital

Who owns TVETENVEIEN 152 MEVLANA 2 AS?

ISMG OSLO-MEVLANA MOSKE
TVETENVEIEN 152 MEVLANA 2 AS
NOK 340,000 rev. · NOK 295,000 profit

TVETENVEIEN 152 MEVLANA 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TVETENVEIEN 152 MEVLANA 2 AS

Who owns TVETENVEIEN 152 MEVLANA 2 AS?

ISMG OSLO-MEVLANA MOSKE is the largest registered owner, with 100.0%.

What is the revenue of TVETENVEIEN 152 MEVLANA 2 AS?

TVETENVEIEN 152 MEVLANA 2 AS had revenue of NOK 340,000 in 2024.

Where is TVETENVEIEN 152 MEVLANA 2 AS based?

TVETENVEIEN 152 MEVLANA 2 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.