BIZTRAC BETA
Rental and operating of own or leased real estate

UNITED INVEST EIENDOM AS

Org. no. 990453136 Limited company (AS) Gjøvik Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.1m
Equity NOK 6.7m
Incorporated 2006
Share capital NOK 262,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

UNITED INVEST EIENDOM AS is registered as a limited company in Gjøvik, Innlandet with organisation number 990453136. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 262,000, divided into 11900 shares. The company's stated purpose is: “Investeringer, herunder kjøp, salg og drift av faste eiendommer, samt å delta som aksjeeier eller på annen måte i andre selskaper. ”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.1m
Equity
NOK 6.7m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns UNITED INVEST EIENDOM AS?

UNITED INVEST AS
UNITED INVEST EIENDOM AS
NOK 2.2m rev. · NOK 1.1m profit

UNITED INVEST EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNITED INVEST EIENDOM AS

Who owns UNITED INVEST EIENDOM AS?

UNITED INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of UNITED INVEST EIENDOM AS?

UNITED INVEST EIENDOM AS had revenue of NOK 2.2m in 2024.

Where is UNITED INVEST EIENDOM AS based?

UNITED INVEST EIENDOM AS has its business address in Hunndalen.

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.