BIZTRAC BETA
Combined facilities support activities

RESSURSTEAM AS

Org. no. 922809372 Limited company (AS) Bamble Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 861,000
Operating profit NOK 763,000
Equity NOK 92,000
Incorporated 2019
Share capital NOK 50,000

RESSURSTEAM AS is registered as a limited company in Bamble, Telemark with organisation number 922809372. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2019. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Tilby et variert sortiment av tjenester overfor private-, offentlige­ og næringslivsaktører. Virksomheten består i renholdstjenester, serviceoppdrag, event-tjenester mv.”. The most recent filed accounts, for the 2024 financial year, show NOK 861,000 in revenue and NOK 763,000 in operating profit.

Key figures · 2024

Revenue
NOK 861,000
Operating profit
NOK 763,000
Equity
NOK 92,000
Est. value
NOK 2.3m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RESSURSTEAM AS?

BRUNSTAD UNGDOMSKLUBB GRENLAND
RESSURSTEAM AS
NOK 861,000 rev. · NOK 763,000 profit

RESSURSTEAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESSURSTEAM AS

Who owns RESSURSTEAM AS?

BRUNSTAD UNGDOMSKLUBB GRENLAND is the largest registered owner, with 100.0%.

What is the revenue of RESSURSTEAM AS?

RESSURSTEAM AS had revenue of NOK 861,000 in 2024.

Who is the general manager of RESSURSTEAM AS?

Edgar Almås is registered as general manager of RESSURSTEAM AS.

Where is RESSURSTEAM AS based?

RESSURSTEAM AS has its business address in Stathelle.

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.