BIZTRAC BETA
Site preparation

REAUS SERVICE AS

Org. no. 918873414 Limited company (AS) Bjørnafjorden Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK 151,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

REAUS SERVICE AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 918873414. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Entrepenør med utleie av personell innen og i nærliggende bransjer. Kjøp, salg og reparasjon av båt og motor, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 151,000
Est. value
NOK 155,000

Financial health · 2024

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

Who owns REAUS SERVICE AS?

REMI AUSTEVOLL
REAUS SERVICE AS
NOK 0 rev. · NOK −14,000 profit

REAUS SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REAUS SERVICE AS own?

REAUS SERVICE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about REAUS SERVICE AS

Who owns REAUS SERVICE AS?

REMI AUSTEVOLL is the largest registered owner, with 100.0%.

What is the revenue of REAUS SERVICE AS?

REAUS SERVICE AS had revenue of NOK 0 in 2024.

Where is REAUS SERVICE AS based?

REAUS SERVICE AS has its business address in Lepsøy.

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.