biztrac. BETA
COMPANY REGISTER PROFILE
923165681 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

SELFIE AS

Org. no. 923165681 Limited company (AS) Tromsø Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 60,000
Operating profit NOK −224,000
Equity NOK 474,000
Incorporated 2019
Share capital NOK 450,000

Signals

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

SELFIE AS is registered as a limited company in Tromsø, Troms with organisation number 923165681. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 450,000, divided into 450 shares. The company's stated purpose is: “Kafé, serveringsvirksomhet og annen virksomhet som står i forbindelse med dette, samt deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 60,000 in revenue and NOK −224,000 in operating profit.

Key figures · 2025

Revenue
NOK 60,000
Operating profit
NOK −224,000
▼ −14 %
Equity
NOK 474,000
▼ −32 %
Est. value
NOK 280,000

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
-31.4%
Not satisfactory
Return on total assets
Solidity
76.1%
Very good
Equity as a share of total capital

Who owns SELFIE AS?

SELFIE AS
NOK 60,000 rev. · NOK −224,000 profit

SELFIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SELFIE AS

Who owns SELFIE AS?

Dessislava Ivanova Ivanova is the largest registered owner, with 50.0%.

What is the revenue of SELFIE AS?

SELFIE AS had revenue of NOK 60,000 in 2025.

Who is the general manager of SELFIE AS?

Dessislava Ivanova Ivanova is registered as general manager of SELFIE AS.

Where is SELFIE AS based?

SELFIE AS has its business address in Tromsø.

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

Report a problem

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