BIZTRAC BETA
Other non-specialised retail sale

BOBLENDE-KREATIVITET AS

Org. no. 936176267 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 74,000
Operating profit NOK 3,000
Equity NOK 56,000
Incorporated 2025
Share capital NOK 60,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-08-27.

BOBLENDE-KREATIVITET AS is registered as a limited company in Stavanger, Rogaland with organisation number 936176267. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Drive med netthandel, og jeg skal selge Hobby og scrappbook utstyr.”.

Key figures

Revenue
NOK 74,000
Operating profit
NOK 3,000
Equity
NOK 56,000
Est. value
NOK 44,000

Financial health · 2025

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

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

Who owns BOBLENDE-KREATIVITET AS?

JORUNN LANGÅS ANDREASSEN
BOBLENDE-KREATIVITET AS
NOK 74,000 rev. · NOK 3,000 profit

BOBLENDE-KREATIVITET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOBLENDE-KREATIVITET AS

Who owns BOBLENDE-KREATIVITET AS?

JORUNN LANGÅS ANDREASSEN is the largest registered owner, with 100.0%.

What is the revenue of BOBLENDE-KREATIVITET AS?

BOBLENDE-KREATIVITET AS had revenue of NOK 74,000.

Who is the general manager of BOBLENDE-KREATIVITET AS?

Jorunn Langås Andreassen is registered as general manager of BOBLENDE-KREATIVITET AS.

Where is BOBLENDE-KREATIVITET AS based?

BOBLENDE-KREATIVITET AS has its business address in Stavanger.

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.