BIZTRAC BETA
Development of building projects

TEAM BYGG AS

Org. no. 984738161 Limited company (AS) Time Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 60.0m
Operating profit NOK −3.1m
Equity NOK 45.7m
Incorporated 2002
Share capital NOK 323,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,1 mill kr).

TEAM BYGG AS is registered as a limited company in Time, Rogaland with organisation number 984738161. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 323,000, divided into 161250 shares. The company's stated purpose is: “Eie, investere i og utvikle eiendom samt deltakelse av enhver art i andre virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 60.0m in revenue and NOK −3.1m in operating profit.

Key figures · 2024

Revenue
NOK 60.0m
Operating profit
NOK −3.1m
Equity
NOK 45.7m
Est. value
NOK 101.1m

Financial health · 2024

Liquidity
10.72
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.1%
Good
Equity as a share of total capital

Who owns TEAM BYGG AS?

QBEN INFRA AB
TEAM BYGG AS
NOK 60.0m rev. · NOK −3.1m profit

TEAM BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEAM BYGG AS own?

TEAM BYGG AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about TEAM BYGG AS

Who owns TEAM BYGG AS?

QBEN INFRA AB is the largest registered owner, with 100.0%.

What is the revenue of TEAM BYGG AS?

TEAM BYGG AS had revenue of NOK 60.0m in 2024.

Who is the general manager of TEAM BYGG AS?

Terje Aasen is registered as general manager of TEAM BYGG AS.

Where is TEAM BYGG AS based?

TEAM BYGG AS has its business address in Bryne.

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.