BIZTRAC BETA
Rental and operating of own or leased real estate

MIDTHJELL EIENDOM AS

Org. no. 915205402 Limited company (AS) Midtre Gauldal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 893,000
Operating profit NOK 164,000
Equity NOK 1.7m
Incorporated 2015
Share capital NOK 50,000

MIDTHJELL EIENDOM AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 915205402. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Investering i fast eiendom, kjøp og salg av aksjer, verdipapirer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 893,000 in revenue and NOK 164,000 in operating profit.

Key figures · 2025

Revenue
NOK 893,000
Operating profit
NOK 164,000
Equity
NOK 1.7m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns MIDTHJELL EIENDOM AS?

MIDTHJELL HOLDING AS
MIDTHJELL EIENDOM AS
NOK 893,000 rev. · NOK 164,000 profit

MIDTHJELL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTHJELL EIENDOM AS

Who owns MIDTHJELL EIENDOM AS?

MIDTHJELL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MIDTHJELL EIENDOM AS?

MIDTHJELL EIENDOM AS had revenue of NOK 893,000 in 2025.

Who is the general manager of MIDTHJELL EIENDOM AS?

Ole Aleksander Midthjell is registered as general manager of MIDTHJELL EIENDOM AS.

Where is MIDTHJELL EIENDOM AS based?

MIDTHJELL EIENDOM AS has its business address in Støren.

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.