BIZTRAC BETA
Rental and operating of own or leased real estate

RAINALS AUNE AS

Org. no. 948319594 Limited company (AS) Sandefjord Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK −8,000
Equity NOK 3.5m
Incorporated 1988
Employees 7
Share capital NOK 144,000

Signals

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

RAINALS AUNE AS is registered as a limited company in Sandefjord, Vestfold with organisation number 948319594. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988 and has 7 registered employees. Registered share capital is NOK 144,000, divided into 1440 shares. The company's stated purpose is: “Å eie eiendommer, drive utleie og virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK −8,000
Equity
NOK 3.5m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns RAINALS AUNE AS?

RAINALS AUNE FORVALTNING AS
RAINALS AUNE AS
NOK 3.5m rev. · NOK −8,000 profit

RAINALS AUNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAINALS AUNE AS

Who owns RAINALS AUNE AS?

RAINALS AUNE FORVALTNING AS is the largest registered owner, with 100.0%.

What is the revenue of RAINALS AUNE AS?

RAINALS AUNE AS had revenue of NOK 3.5m in 2024.

Who is the general manager of RAINALS AUNE AS?

Helle Rainals Aune is registered as general manager of RAINALS AUNE AS.

Where is RAINALS AUNE AS based?

RAINALS AUNE AS has its business address in Sandefjord.

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.