biztrac. BETA
COMPANY REGISTER PROFILE
997991672 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TOTALBYGG TELEMARK AS

Org. no. 997991672 Limited company (AS) Porsgrunn Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −195,000
Equity NOK 282,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

TOTALBYGG TELEMARK AS is registered as a limited company in Porsgrunn, Telemark with organisation number 997991672. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Byggevirksomhet med tilhørende tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −195,000 in operating profit.

Former names: XT BYGG AS

Key figures · 2025

Revenue
NOK 1.8m
▼ −92 %
Operating profit
NOK −195,000
▼ −52 %
Equity
NOK 282,000
▼ −58 %
Est. value
NOK 761,000

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
-6.6%
Not satisfactory
Return on total assets
Solidity
33.4%
Good
Equity as a share of total capital

Who owns TOTALBYGG TELEMARK AS?

TOTALBYGG TELEMARK AS
NOK 1.8m rev. · NOK −195,000 profit

TOTALBYGG TELEMARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOTALBYGG TELEMARK AS

Who owns TOTALBYGG TELEMARK AS?

ESCENDO AS is the largest registered owner, with 100.0%.

What is the revenue of TOTALBYGG TELEMARK AS?

TOTALBYGG TELEMARK AS had revenue of NOK 1.8m in 2025.

Where is TOTALBYGG TELEMARK AS based?

TOTALBYGG TELEMARK AS has its business address in Porsgrunn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.