BIZTRAC BETA
Site preparation

REIME ENTREPRENØR AS

Org. no. 989582992 Limited company (AS) Voss Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 653,000
Operating profit NOK −32,000
Equity NOK −205,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

REIME ENTREPRENØR AS is registered as a limited company in Voss, Vestland with organisation number 989582992. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 653,000 in revenue and NOK −32,000 in operating profit.

Key figures · 2024

Revenue
NOK 653,000
Operating profit
NOK −32,000
Equity
NOK −205,000

Financial health · 2024

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

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

Who owns REIME ENTREPRENØR AS?

TORGEIR REIME
REIME ENTREPRENØR AS
NOK 653,000 rev. · NOK −32,000 profit

REIME ENTREPRENØR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about REIME ENTREPRENØR AS

Who owns REIME ENTREPRENØR AS?

TORGEIR REIME is the largest registered owner, with 65.0%.

What is the revenue of REIME ENTREPRENØR AS?

REIME ENTREPRENØR AS had revenue of NOK 653,000 in 2024.

Who is the general manager of REIME ENTREPRENØR AS?

Torgeir Reime is registered as general manager of REIME ENTREPRENØR AS.

Where is REIME ENTREPRENØR AS based?

REIME ENTREPRENØR AS has its business address in Voss.

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.