BIZTRAC BETA
Construction of residential and non-residential buildings

PH BYGG AS

Org. no. 930078077 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 20.9m
Operating profit NOK 3.7m
Equity NOK 3.2m
Incorporated 2022
Employees 21
Share capital NOK 30,000

PH BYGG AS is registered as a limited company in Kristiansand, Agder with organisation number 930078077. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 21 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Oppføring av bygninger og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.9m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 20.9m
Operating profit
NOK 3.7m
Equity
NOK 3.2m
Est. value
NOK 12.1m

Financial health · 2024

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

Who owns PH BYGG AS?

PEOPLEHUB HOLDING AS
PH BYGG AS
NOK 20.9m rev. · NOK 3.7m profit

PH BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PH BYGG AS

Who owns PH BYGG AS?

PEOPLEHUB HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PH BYGG AS?

PH BYGG AS had revenue of NOK 20.9m in 2024.

Who is the general manager of PH BYGG AS?

Adomas Zagarnauskas is registered as general manager of PH BYGG AS.

Where is PH BYGG AS based?

PH BYGG AS has its business address in Hamresanden.

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.