BIZTRAC BETA
Installation of insulation

MIDT-NORGE BLÅSEISOLERING AS

Org. no. 927440288 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 635,000
Equity NOK 1.2m
Incorporated 2021
Share capital NOK 30,000

MIDT-NORGE BLÅSEISOLERING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927440288. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Spesialisering innen bygge- og anleggsvirksomhet, samt annen utførelse som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 635,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
Operating profit
NOK 635,000
Equity
NOK 1.2m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns MIDT-NORGE BLÅSEISOLERING AS?

FULL TRØKK AS
MIDT-NORGE BLÅSEISOLERING AS
NOK 9.4m rev. · NOK 635,000 profit

MIDT-NORGE BLÅSEISOLERING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MIDT-NORGE BLÅSEISOLERING AS

Who owns MIDT-NORGE BLÅSEISOLERING AS?

FULL TRØKK AS is the largest registered owner, with 45.0%.

What is the revenue of MIDT-NORGE BLÅSEISOLERING AS?

MIDT-NORGE BLÅSEISOLERING AS had revenue of NOK 9.4m in 2025.

Who is the general manager of MIDT-NORGE BLÅSEISOLERING AS?

Stian Norby is registered as general manager of MIDT-NORGE BLÅSEISOLERING AS.

Where is MIDT-NORGE BLÅSEISOLERING AS based?

MIDT-NORGE BLÅSEISOLERING AS has its business address in Ranheim.

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.