BIZTRAC BETA
Construction of residential and non-residential buildings

TOTALBYGG TELEMARK AS

Org. no. 997991672 Limited company (AS) Porsgrunn Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 21.8m
Operating profit NOK −129,000
Equity NOK 672,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−129k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

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 2024 financial year, show NOK 21.8m in revenue and NOK −129,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.8m
Operating profit
NOK −129,000
Equity
NOK 672,000
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns TOTALBYGG TELEMARK AS?

ESCENDO AS
TOTALBYGG TELEMARK AS
NOK 21.8m rev. · NOK −129,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 21.8m in 2024.

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 15.06.2026.

Report a problem

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