BIZTRAC BETA
Installation of insulation

BYGG ISO-TERM AS

Org. no. 993547492 Limited company (AS) Indre Fosen Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK −4,000
Equity NOK 184,000
Incorporated 2009
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

BYGG ISO-TERM AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 993547492. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2009. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Termografering, isolering av bygg, kvalitetskontroll av bygg og ellers det som naturlig hører til. I tillegg vil selskapet drive med kjøp av aksjer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK −4,000
Equity
NOK 184,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.3%
Satisfactory
Equity as a share of total capital

Who owns BYGG ISO-TERM AS?

SVEIN BREDESEN
BYGG ISO-TERM AS
NOK 2.8m rev. · NOK −4,000 profit

BYGG ISO-TERM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGG ISO-TERM AS

Who owns BYGG ISO-TERM AS?

SVEIN BREDESEN is the largest registered owner, with 75.0%.

What is the revenue of BYGG ISO-TERM AS?

BYGG ISO-TERM AS had revenue of NOK 2.8m in 2025.

Who is the general manager of BYGG ISO-TERM AS?

Svein Bredesen is registered as general manager of BYGG ISO-TERM AS.

Where is BYGG ISO-TERM AS based?

BYGG ISO-TERM AS has its business address in Rissa.

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.