BIZTRAC BETA
COMPANY REGISTER PROFILE
921634765 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
All other professional, scientific and technical activities n.e.c.

LEX IULIA AS

Org. no. 921634765 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2018
Share capital NOK 30,000

LEX IULIA AS is registered as a limited company in Stavanger, Rogaland with organisation number 921634765. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rådgivning innen geografisk informasjon.”.

Key figures · 2025

Equity
NOK 30,000
▲ +0 %
Est. value
NOK 49,000

Financial health · 2025

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

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

Who owns LEX IULIA AS?

LEX IULIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEX IULIA AS

Who owns LEX IULIA AS?

NJÅL TENGS-HAGIR is the largest registered owner, with 100.0%.

Who is the general manager of LEX IULIA AS?

Njål Tengs-Hagir is registered as general manager of LEX IULIA AS.

Where is LEX IULIA AS based?

LEX IULIA AS has its business address in Stavanger.

Property

Business address Gangarstien 15, 4021 Stavanger
Cadastral unit 1103-25/71/0/0
Building Tomannsbolig, vertikal · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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