BIZTRAC BETA
Rental and operating of own or leased real estate

MUNKEGT. 25 AS

Org. no. 930168203 Limited company (AS) Trondheim Incorporated 1962 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 681,000
Equity NOK 5.8m
Incorporated 1962
Share capital NOK 150,000

MUNKEGT. 25 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930168203. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1962. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Eie samt forvaltning av eiendommen Munkegata 25 samt å drive med kjøp, salg og forvaltning av andre faste eiendommer og alt som hermed står i forbindelse. Videre er selskapets formål ved aksjetegning eller på annen måte å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 681,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 681,000
Equity
NOK 5.8m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns MUNKEGT. 25 AS?

TOKLE AS
MUNKEGT. 25 AS
NOK 2.4m rev. · NOK 681,000 profit

MUNKEGT. 25 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MUNKEGT. 25 AS

Who owns MUNKEGT. 25 AS?

TOKLE AS is the largest registered owner, with 50.0%.

What is the revenue of MUNKEGT. 25 AS?

MUNKEGT. 25 AS had revenue of NOK 2.4m in 2024.

Who is the general manager of MUNKEGT. 25 AS?

Georg Michael Tokle Minervini is registered as general manager of MUNKEGT. 25 AS.

Where is MUNKEGT. 25 AS based?

MUNKEGT. 25 AS has its business address in Trondheim.

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.