BIZTRAC BETA
Rental and operating of own or leased real estate

GRENSEVEIEN UNDERVISNINGSBYGG AS

Org. no. 925031445 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −203,000
Equity NOK 139.3m
Incorporated 2020
Share capital NOK 1.8m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−203k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRENSEVEIEN UNDERVISNINGSBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 925031445. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 1.8m, divided into 18400000 shares. The company's stated purpose is: “Investere i og eie aksjer eller andeler i selskap som eier fast eiendom og hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −203,000
Equity
NOK 139.3m
Est. value
NOK 160.6m

Financial health · 2025

Liquidity
5.35
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.0%
Good
Equity as a share of total capital

Who owns GRENSEVEIEN UNDERVISNINGSBYGG AS?

NEXTNET AS
GRENSEVEIEN UNDERVISNINGSBYGG AS
· NOK −203,000 profit

GRENSEVEIEN UNDERVISNINGSBYGG AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does GRENSEVEIEN UNDERVISNINGSBYGG AS own?

GRENSEVEIEN UNDERVISNINGSBYGG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GRENSEVEIEN UNDERVISNINGSBYGG AS

Who owns GRENSEVEIEN UNDERVISNINGSBYGG AS?

NEXTNET AS is the largest registered owner, with 10.0%.

Where is GRENSEVEIEN UNDERVISNINGSBYGG AS based?

GRENSEVEIEN UNDERVISNINGSBYGG AS has its business address in Oslo.

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.