BIZTRAC BETA
Construction of residential and non-residential buildings

LITZHEIM EIENDOM OG BOLIGUTVIKLING AS

Org. no. 916863152 Limited company (AS) Ullensaker Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 324,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

LITZHEIM EIENDOM OG BOLIGUTVIKLING AS is registered as a limited company in Ullensaker, Akershus with organisation number 916863152. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bolig og hytteutbygging, kjøp og salg av eiendom og tomter. Utleie av bolig og hytte/fritidseiendommer, samt rådgivning innen bygg og anlegg.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK 324,000
Est. value
NOK 332,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
93.1%
Very good
Equity as a share of total capital

Who owns LITZHEIM EIENDOM OG BOLIGUTVIKLING AS?

TERJE LITZHEIM
LITZHEIM EIENDOM OG BOLIGUTVIKLING AS
· NOK −2,000 profit

LITZHEIM EIENDOM OG BOLIGUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LITZHEIM EIENDOM OG BOLIGUTVIKLING AS

Who owns LITZHEIM EIENDOM OG BOLIGUTVIKLING AS?

TERJE LITZHEIM is the largest registered owner, with 50.0%.

Who is the general manager of LITZHEIM EIENDOM OG BOLIGUTVIKLING AS?

Terje Litzheim is registered as general manager of LITZHEIM EIENDOM OG BOLIGUTVIKLING AS.

Where is LITZHEIM EIENDOM OG BOLIGUTVIKLING AS based?

LITZHEIM EIENDOM OG BOLIGUTVIKLING AS has its business address in Kløfta.

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.