biztrac. BETA
COMPANY REGISTER PROFILE
997851080 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

REIN AS

Org. no. 997851080 Limited company (AS) Gjesdal Incorporated 2012 Active
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 5.9m
Incorporated 2012
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

REIN AS is registered as a limited company in Gjesdal, Rogaland with organisation number 997851080. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Investere i andre selskaper, verdipapirer og eiendom samt tilby konsulenttjenester og det som ligger naturlig dertil.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Former names: PANTHEON CAPITAL AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
▲ +58 %
Equity
NOK 5.9m
▼ −0 %
Est. value
NOK 5.4m

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
69.4%
Very good
Equity as a share of total capital

Who owns REIN AS?

REIN AS
NOK 0 rev. · NOK −18,000 profit

REIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REIN AS own?

REIN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about REIN AS

Who owns REIN AS?

Christoffer Rein Salvesen is the largest registered owner, with 100.0%.

What is the revenue of REIN AS?

REIN AS had revenue of NOK 0 in 2025.

Where is REIN AS based?

REIN AS has its business address in Ålgård.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.