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

JELLESTADVEIEN 1 SEKSJON 1 AS

Org. no. 929027418 Limited company (AS) Kongsvinger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −122,000
Equity NOK −57,000
Incorporated 2022
Share capital NOK 230,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−57k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−122k kr).
  • Nylig endring 2026-07-24 Adresseendring registrert 2026-07-24.

JELLESTADVEIEN 1 SEKSJON 1 AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 929027418. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 230,000, divided into 4 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −122,000
▲ +23 %
Equity
NOK −57,000
▼ −253 %

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1.6%
Weak
Equity as a share of total capital

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

Who owns JELLESTADVEIEN 1 SEKSJON 1 AS?

JELLESTADVEIEN 1 SEKSJON 1 AS
· NOK −122,000 profit

JELLESTADVEIEN 1 SEKSJON 1 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JELLESTADVEIEN 1 SEKSJON 1 AS

Who owns JELLESTADVEIEN 1 SEKSJON 1 AS?

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

Where is JELLESTADVEIEN 1 SEKSJON 1 AS based?

JELLESTADVEIEN 1 SEKSJON 1 AS has its business address in Kongsvinger.

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.