BIZTRAC BETA
Rental and operating of own or leased real estate

FIRST EIENDOM INVEST AS

Org. no. 930120065 Limited company (AS) Kongsvinger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −229,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−229k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

FIRST EIENDOM INVEST AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 930120065. 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 30,000, divided into 1000 shares. The company's stated purpose is: “Erverve, eie og forvalte aksjer i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK −229,000

Financial health · 2024

Liquidity
7.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.8%
Weak
Equity as a share of total capital

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

Who owns FIRST EIENDOM INVEST AS?

Per Helge Jakobsen
FIRST EIENDOM INVEST AS
· NOK −5,000 profit

FIRST EIENDOM INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIRST EIENDOM INVEST AS own?

FIRST EIENDOM INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FIRST EIENDOM INVEST AS

Who owns FIRST EIENDOM INVEST AS?

Per Helge Jakobsen is the largest registered owner, with 100.0%.

Who is the general manager of FIRST EIENDOM INVEST AS?

Per Helge Jakobsen is registered as general manager of FIRST EIENDOM INVEST AS.

Where is FIRST EIENDOM INVEST AS based?

FIRST EIENDOM INVEST 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.