biztrac. BETA
COMPANY REGISTER PROFILE
925731889 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MT FORT INVEST AS

Org. no. 925731889 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 353,000
Operating profit NOK 156,000
Equity NOK 3.6m
Incorporated 2020
Share capital NOK 500,000

MT FORT INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 925731889. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Kjøp og salg av aksjer, investere i fast eiendom, forvaltning av kapital, herunder utlån og garantistillelser samt deltakelse i andre selskaper og dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 353,000 in revenue and NOK 156,000 in operating profit.

Key figures · 2025

Revenue
NOK 353,000
▲ +7 %
Operating profit
NOK 156,000
▲ +11 %
Equity
NOK 3.6m
▲ +37 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
43.9%
Very good
Equity as a share of total capital

Who owns MT FORT INVEST AS?

MT FORT INVEST AS
NOK 353,000 rev. · NOK 156,000 profit

MT FORT INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MT FORT INVEST AS own?

MT FORT INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MT FORT INVEST AS

Who owns MT FORT INVEST AS?

FJELLSTØTT INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of MT FORT INVEST AS?

MT FORT INVEST AS had revenue of NOK 353,000 in 2025.

Where is MT FORT INVEST AS based?

MT FORT INVEST 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.