BIZTRAC BETA
COMPANY REGISTER PROFILE
933243435 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

LISTENALERT AS

Org. no. 933243435 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 105,000
Operating profit NOK −308,000
Equity NOK 216,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−308k kr).

LISTENALERT AS is registered as a limited company in Oslo, Oslo with organisation number 933243435. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programmering og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 105,000 in revenue and NOK −308,000 in operating profit.

Key figures · 2024

Revenue
NOK 105,000
Operating profit
NOK −308,000
Equity
NOK 216,000
Est. value
NOK 244,000

Financial health · 2024

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

Who owns LISTENALERT AS?

No shareholders are registered for LISTENALERT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LISTENALERT AS

What is the revenue of LISTENALERT AS?

LISTENALERT AS had revenue of NOK 105,000 in 2024.

Who is the general manager of LISTENALERT AS?

Nicholas Alexander Kristoffersen is registered as general manager of LISTENALERT AS.

Where is LISTENALERT AS based?

LISTENALERT AS has its business address in Oslo.

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.