BIZTRAC BETA
Construction of residential and non-residential buildings

TWR BYGG AS

Org. no. 921310013 Limited company (AS) Arendal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −614,000
Equity NOK 187,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

TWR BYGG AS is registered as a limited company in Arendal, Agder with organisation number 921310013. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygg, vedlikehold, servicetjenester og ledelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −614,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −614,000
Equity
NOK 187,000
Est. value
NOK 550,000

Financial health · 2024

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

Who owns TWR BYGG AS?

TR INVEST AS
TWR BYGG AS
NOK 1.4m rev. · NOK −614,000 profit

TWR BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TWR BYGG AS

Who owns TWR BYGG AS?

TR INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TWR BYGG AS?

TWR BYGG AS had revenue of NOK 1.4m in 2024.

Who is the general manager of TWR BYGG AS?

Trond Einar Wiker Rønningen is registered as general manager of TWR BYGG AS.

Where is TWR BYGG AS based?

TWR BYGG AS has its business address in Arendal.

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.