BIZTRAC BETA
Activities of advertising agencies

IDENTETY AS

Org. no. 917001618 Limited company (AS) Sandefjord Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −239,000
Equity NOK −398,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−398k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−239k kr).

IDENTETY AS is registered as a limited company in Sandefjord, Vestfold with organisation number 917001618. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reklame og profilering innenfor salg, handel, innkjøp, samt ved alt som står i forbindelse. Videre ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −239,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −239,000
Equity
NOK −398,000

Financial health · 2024

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

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

Who owns IDENTETY AS?

HK HOLDING (HEIDI KLEVSTAD) AS
IDENTETY AS
NOK 1.1m rev. · NOK −239,000 profit

IDENTETY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about IDENTETY AS

Who owns IDENTETY AS?

HK HOLDING (HEIDI KLEVSTAD) AS is the largest registered owner, with 53.3%.

What is the revenue of IDENTETY AS?

IDENTETY AS had revenue of NOK 1.1m in 2024.

Where is IDENTETY AS based?

IDENTETY AS has its business address in Stokke.

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.