BIZTRAC BETA
COMPANY REGISTER PROFILE
921705263 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

UNNALITT AS

Org. no. 921705263 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −58,000
Equity NOK 4.7m
Incorporated 2018
Share capital NOK 30,000

Signals

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

UNNALITT AS is registered as a limited company in Oslo, Oslo with organisation number 921705263. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Generell investeringsvirksomhet, herunder investering i verdipapirer, valuta, eiendommer, andeler, etc., samt delta i eller eie selskaper med beslektet virksomhet.”.

Key figures · 2025

Operating profit
NOK −58,000
Equity
NOK 4.7m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns UNNALITT AS?

UNNALITT AS
· NOK −58,000 profit

UNNALITT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNNALITT AS

Who owns UNNALITT AS?

SIMEN ESPESETH SANDBERG is the largest registered owner, with 100.0%.

Where is UNNALITT AS based?

UNNALITT AS has its business address in Oslo.

Property

Business address c/o Simen Espeseth Sandberg Oppsal terrasse 17, 0686 Oslo
Cadastral unit 301-146/583/0/0
Building Kjede/atriumhus · 1 unit

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.