BIZTRAC BETA
Construction of residential and non-residential buildings

TORGERSEN BYGG AS

Org. no. 833075152 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 157,000
Equity NOK 192,000
Incorporated 2024
Share capital NOK 30,000

TORGERSEN BYGG AS is registered as a limited company in Kristiansand, Agder with organisation number 833075152. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby tømrertjenester, inkludert, men ikke begrenset til, oppføring, vedlikehold, og reparasjon av bygninger, konstruksjon av trestrukturer, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 157,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 157,000
Equity
NOK 192,000
Est. value
NOK 619,000

Financial health · 2025

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

Who owns TORGERSEN BYGG AS?

PÅL TORGERSEN
TORGERSEN BYGG AS
NOK 4.2m rev. · NOK 157,000 profit

TORGERSEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORGERSEN BYGG AS

Who owns TORGERSEN BYGG AS?

PÅL TORGERSEN is the largest registered owner, with 100.0%.

What is the revenue of TORGERSEN BYGG AS?

TORGERSEN BYGG AS had revenue of NOK 4.2m in 2025.

Who is the general manager of TORGERSEN BYGG AS?

Pål Torgersen is registered as general manager of TORGERSEN BYGG AS.

Where is TORGERSEN BYGG AS based?

TORGERSEN BYGG AS has its business address in Flekkerøy.

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.