BIZTRAC BETA
Rental and operating of own or leased real estate

GRENI ØSTRE AS

Org. no. 981187067 Limited company (AS) Nes Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 974,000
Operating profit NOK 610,000
Equity NOK 3.4m
Incorporated 1999
Share capital NOK 850,000

GRENI ØSTRE AS is registered as a limited company in Nes, Akershus with organisation number 981187067. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 850,000, divided into 170 shares. The company's stated purpose is: “Langsiktige investeringer i finans aktiva samt real aktiva. selskapet vil forvalte utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 974,000 in revenue and NOK 610,000 in operating profit.

Key figures · 2024

Revenue
NOK 974,000
Operating profit
NOK 610,000
Equity
NOK 3.4m
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns GRENI ØSTRE AS?

OLE ALBERT BØHN
GRENI ØSTRE AS
NOK 974,000 rev. · NOK 610,000 profit

GRENI ØSTRE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRENI ØSTRE AS own?

GRENI ØSTRE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GRENI ØSTRE AS

Who owns GRENI ØSTRE AS?

OLE ALBERT BØHN is the largest registered owner, with 100.0%.

What is the revenue of GRENI ØSTRE AS?

GRENI ØSTRE AS had revenue of NOK 974,000 in 2024.

Who is the general manager of GRENI ØSTRE AS?

Ole Albert Bøhn is registered as general manager of GRENI ØSTRE AS.

Where is GRENI ØSTRE AS based?

GRENI ØSTRE AS has its business address in Vormsund.

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.