BIZTRAC BETA
Construction of residential and non-residential buildings

BYGG TERMO AS

Org. no. 913061926 Limited company (AS) Sandnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 271,000
Equity NOK 1.4m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

BYGG TERMO AS is registered as a limited company in Sandnes, Rogaland with organisation number 913061926. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Byggefirma, bygging og reparasjon, samt vedlikehold av bygg og oppføring av grunnmurer med mer. Herunder også å kunne delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 271,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 271,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns BYGG TERMO AS?

INGUNN MOI HAUGEN
BYGG TERMO AS
NOK 2.9m rev. · NOK 271,000 profit

BYGG TERMO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGG TERMO AS

Who owns BYGG TERMO AS?

INGUNN MOI HAUGEN is the largest registered owner, with 50.0%.

What is the revenue of BYGG TERMO AS?

BYGG TERMO AS had revenue of NOK 2.9m in 2025.

Who is the general manager of BYGG TERMO AS?

Johannes Haugen is registered as general manager of BYGG TERMO AS.

Where is BYGG TERMO AS based?

BYGG TERMO AS has its business address in Sandnes.

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.