BIZTRAC BETA
Development of building projects

LAGERSEKSJONER KONGSVINGER AS

Org. no. 926713698 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 18,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

LAGERSEKSJONER KONGSVINGER AS is registered as a limited company in Oslo, Oslo with organisation number 926713698. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverv, utvikling, forvaltning og omsetning av næringseiendom, herunder deltakelse i prosjekter.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK 18,000
Est. value
NOK 16,000

Financial health · 2024

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

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

Who owns LAGERSEKSJONER KONGSVINGER AS?

LAGERSEKSJONER ØST AS
LAGERSEKSJONER KONGSVINGER AS
· NOK −12,000 profit

LAGERSEKSJONER KONGSVINGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAGERSEKSJONER KONGSVINGER AS

Who owns LAGERSEKSJONER KONGSVINGER AS?

LAGERSEKSJONER ØST AS is the largest registered owner, with 100.0%.

Who is the general manager of LAGERSEKSJONER KONGSVINGER AS?

Knut Hegge is registered as general manager of LAGERSEKSJONER KONGSVINGER AS.

Where is LAGERSEKSJONER KONGSVINGER AS based?

LAGERSEKSJONER KONGSVINGER 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.