BIZTRAC BETA
Construction of residential and non-residential buildings

TEAM REFSNES AS

Org. no. 976563123 Limited company (AS) Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 37.6m
Operating profit NOK 3.0m
Equity NOK 2.5m
Incorporated 1996
Employees 15
Share capital NOK 138,000

TEAM REFSNES AS is registered as a limited company in Hå, Rogaland with organisation number 976563123. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1996 and has 15 registered employees. Registered share capital is NOK 138,000, divided into 1380 shares. The company's stated purpose is: “Byggevarehandel og alt som har forbindelse herved.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.6m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 37.6m
Operating profit
NOK 3.0m
Equity
NOK 2.5m
Est. value
NOK 10.9m

Financial health · 2024

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

Who owns TEAM REFSNES AS?

TEAM REFSNES HOLDING AS
TEAM REFSNES AS
NOK 37.6m rev. · NOK 3.0m profit

TEAM REFSNES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEAM REFSNES AS own?

TEAM REFSNES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TEAM REFSNES AS

Who owns TEAM REFSNES AS?

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

What is the revenue of TEAM REFSNES AS?

TEAM REFSNES AS had revenue of NOK 37.6m in 2024.

Who is the general manager of TEAM REFSNES AS?

Arild Refsnes is registered as general manager of TEAM REFSNES AS.

Where is TEAM REFSNES AS based?

TEAM REFSNES AS has its business address in Nærbø.

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.