BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

REALCREW AS

Org. no. 997433629 Limited company (AS) Tønsberg Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK −596,000
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−596k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

REALCREW AS is registered as a limited company in Tønsberg, Vestfold with organisation number 997433629. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utleie av arbeidskraft, konsulentvirksomhet, rådgivning, rekruttering, bemanning og aktiviteter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet. Samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagner.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK −596,000

Financial health · 2024

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

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

Who owns REALCREW AS?

Ole Tom Bugge
REALCREW AS
· NOK −12,000 profit

REALCREW AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REALCREW AS

Who owns REALCREW AS?

Ole Tom Bugge is the largest registered owner, with 100.0%.

Who is the general manager of REALCREW AS?

Ole Tom Bugge is registered as general manager of REALCREW AS.

Where is REALCREW AS based?

REALCREW AS has its business address in Våle.

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.