BIZTRAC BETA
Steam and air conditioning supply

SIT GEOVARME AS

Org. no. 914601630 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 1.4m
Equity NOK 1.2m
Incorporated 2014
Share capital NOK 500,000

SIT GEOVARME AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914601630. The business is classified under steam and air conditioning supply (NACE 35.300). The company was incorporated in 2014. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Produksjon og salg av termisk energi og alt som dermed står i forbindelse. Selskapet er en del av Studentsamskipnaden i Trondheim (SiT) og skal bidra til studentvelferd ved å tilby vannbåren varme til SiTs studentboliger, barnehage og biblioteksbygg på Moholt og andre eiendommer der dette er naturlig. Selskapet skal ikke ha erverv til formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 1.4m
Equity
NOK 1.2m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns SIT GEOVARME AS?

No shareholders are registered for SIT GEOVARME AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SIT GEOVARME AS

What is the revenue of SIT GEOVARME AS?

SIT GEOVARME AS had revenue of NOK 3.2m in 2024.

Who is the general manager of SIT GEOVARME AS?

Lisbeth Glørstad Aspås is registered as general manager of SIT GEOVARME AS.

Where is SIT GEOVARME AS based?

SIT GEOVARME 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.