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

GRS INVEST AS

Org. no. 918495479 Limited company (AS) Skien Incorporated 2017 Active
Revenue 2025 NOK 864,000
Operating profit NOK 561,000
Equity NOK 325,000
Incorporated 2017
Share capital NOK 30,000

GRS INVEST AS is registered as a limited company in Skien, Telemark with organisation number 918495479. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskaper, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 864,000 in revenue and NOK 561,000 in operating profit.

Key figures · 2025

Revenue
NOK 864,000
▲ +28 %
Operating profit
NOK 561,000
▲ +37 %
Equity
NOK 325,000
▲ +72 %
Est. value
NOK 798,000

Financial health · 2025

Liquidity
2.07
Very good
Current assets ÷ current liabilities
Profitability
7.8%
Satisfactory
Return on total assets
Solidity
4.5%
Weak
Equity as a share of total capital

Who owns GRS INVEST AS?

GRS INVEST AS
NOK 864,000 rev. · NOK 561,000 profit

GRS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRS INVEST AS

Who owns GRS INVEST AS?

Alexander Øygarden is the largest registered owner, with 100.0%.

What is the revenue of GRS INVEST AS?

GRS INVEST AS had revenue of NOK 864,000 in 2025.

Who is the general manager of GRS INVEST AS?

Alexander Øygarden is registered as general manager of GRS INVEST AS.

Where is GRS INVEST AS based?

GRS INVEST AS has its business address in Skien.

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.