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

RAPPOR AS

Org. no. 976065786 Limited company (AS) Stavanger Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −36,000
Equity NOK 9.7m
Incorporated 1996
Share capital NOK 100,000

Signals

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

RAPPOR AS is registered as a limited company in Stavanger, Rogaland with organisation number 976065786. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Investeringer i verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −36,000
▼ −27 %
Equity
NOK 9.7m
▲ +15 %
Est. value
NOK 13.4m

Financial health · 2025

Liquidity
18.96
Very good
Current assets ÷ current liabilities
Profitability
19.3%
Very good
Return on total assets
Solidity
95.1%
Very good
Equity as a share of total capital

Who owns RAPPOR AS?

RAPPOR AS has 4 registered shareholders:

All shareholders and roles →

Which companies does RAPPOR AS own?

RAPPOR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RAPPOR AS

Who owns RAPPOR AS?

Nikolai Røtnes Bratteli is the largest registered owner, with 25.0%.

What is the revenue of RAPPOR AS?

RAPPOR AS had revenue of NOK 0 in 2025.

Who is the general manager of RAPPOR AS?

Egil Bratteli is registered as general manager of RAPPOR AS.

Where is RAPPOR AS based?

RAPPOR AS has its business address in Stavanger.

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.