BIZTRAC BETA
Computer programming activities

BLOOMLET TECHNOLOGIES AS

Org. no. 933063976 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.2m
Equity NOK −1.1m
Incorporated 2024
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

BLOOMLET TECHNOLOGIES AS is registered as a limited company in Trondheim, Trøndelag with organisation number 933063976. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 1000000 shares. The company's stated purpose is: “Utvikle og drifte teknologiske løsninger og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.2m
Equity
NOK −1.1m

Financial health · 2024

Liquidity
2.39
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-30.0%
Weak
Equity as a share of total capital

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

Who owns BLOOMLET TECHNOLOGIES AS?

LORENSE HOLDING AS
BLOOMLET TECHNOLOGIES AS
NOK 0 rev. · NOK −1.2m profit

BLOOMLET TECHNOLOGIES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOOMLET TECHNOLOGIES AS

Who owns BLOOMLET TECHNOLOGIES AS?

LORENSE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BLOOMLET TECHNOLOGIES AS?

BLOOMLET TECHNOLOGIES AS had revenue of NOK 0 in 2024.

Where is BLOOMLET TECHNOLOGIES AS based?

BLOOMLET TECHNOLOGIES AS has its business address in Trondheim.

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.