BIZTRAC BETA
Rental and operating of own or leased real estate

GRENSEVEIEN 3 AS

Org. no. 918595392 Limited company (AS) Kongsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 2.4m
Equity NOK 4.8m
Incorporated 2017
Share capital NOK 4.5m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-21 Adresseendring registrert 2026-02-21.

GRENSEVEIEN 3 AS is registered as a limited company in Kongsberg, Buskerud with organisation number 918595392. 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 4.5m, divided into 45000 shares. The company's stated purpose is: “Investering i, utleie og utvikling av fast eiendom, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 2.4m
Equity
NOK 4.8m
Est. value
NOK 7.5m

Financial health · 2025

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

Who owns GRENSEVEIEN 3 AS?

ØSTLANDSKE EIENDOMMER AS
GRENSEVEIEN 3 AS
NOK 3.2m rev. · NOK 2.4m profit

GRENSEVEIEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRENSEVEIEN 3 AS

Who owns GRENSEVEIEN 3 AS?

ØSTLANDSKE EIENDOMMER AS is the largest registered owner, with 100.0%.

What is the revenue of GRENSEVEIEN 3 AS?

GRENSEVEIEN 3 AS had revenue of NOK 3.2m in 2025.

Where is GRENSEVEIEN 3 AS based?

GRENSEVEIEN 3 AS has its business address in Kongsberg.

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.