BIZTRAC BETA
Rental and operating of own or leased real estate

GREV EIENDOMSINVEST AS

Org. no. 911838931 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 421,000
Operating profit NOK 328,000
Equity NOK 98,000
Incorporated 2013
Share capital NOK 30,000

GREV EIENDOMSINVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 911838931. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av eiendom, utvikling og drift av eiendommer, samt delta i andre selskaper og konsulenttjenester innen bygg og anleggsbransjen eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 421,000 in revenue and NOK 328,000 in operating profit.

Key figures · 2025

Revenue
NOK 421,000
Operating profit
NOK 328,000
Equity
NOK 98,000
Est. value
NOK 468,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Weak
Equity as a share of total capital

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

Who owns GREV EIENDOMSINVEST AS?

JAAN EIENDOM AS
GREV EIENDOMSINVEST AS
NOK 421,000 rev. · NOK 328,000 profit

GREV EIENDOMSINVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GREV EIENDOMSINVEST AS

Who owns GREV EIENDOMSINVEST AS?

JAAN EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of GREV EIENDOMSINVEST AS?

GREV EIENDOMSINVEST AS had revenue of NOK 421,000 in 2025.

Where is GREV EIENDOMSINVEST AS based?

GREV EIENDOMSINVEST AS has its business address in Barkåker.

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.