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

REISA GRILLHUS AS

Org. no. 915080022 Limited company (AS) Sørreisa Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 305,000
Operating profit NOK −2,000
Equity NOK −139,000
Incorporated 2015
Share capital NOK 1.1m

Signals

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

REISA GRILLHUS AS is registered as a limited company in Sørreisa, Troms with organisation number 915080022. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 305,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 305,000
▲ +2676 %
Operating profit
NOK −2,000
▼ −118 %
Equity
NOK −139,000
▼ −1 %

Financial health · 2025

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

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

Who owns REISA GRILLHUS AS?

REISA GRILLHUS AS
NOK 305,000 rev. · NOK −2,000 profit

REISA GRILLHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REISA GRILLHUS AS

Who owns REISA GRILLHUS AS?

NIELVE AS is the largest registered owner, with 100.0%.

What is the revenue of REISA GRILLHUS AS?

REISA GRILLHUS AS had revenue of NOK 305,000 in 2025.

Where is REISA GRILLHUS AS based?

REISA GRILLHUS AS has its business address in Sørreisa.

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.