BIZTRAC BETA
COMPANY REGISTER PROFILE
929263111 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Retail sale of clothing

LIVID LAVA AS

Org. no. 929263111 Limited company (AS) Time Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −30,000
Equity NOK −37,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−37k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).

LIVID LAVA AS is registered as a limited company in Time, Rogaland with organisation number 929263111. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av klær og interiørartikler via nettbutikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK −37,000

Financial health · 2025

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

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

Who owns LIVID LAVA AS?

KINE HANSEN WIK
LIVID LAVA AS
NOK 0 rev. · NOK −30,000 profit

LIVID LAVA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIVID LAVA AS

Who owns LIVID LAVA AS?

KINE HANSEN WIK is the largest registered owner, with 100.0%.

What is the revenue of LIVID LAVA AS?

LIVID LAVA AS had revenue of NOK 0 in 2025.

Who is the general manager of LIVID LAVA AS?

Kine Hansen Wik is registered as general manager of LIVID LAVA AS.

Where is LIVID LAVA AS based?

LIVID LAVA AS has its business address in Bryne.

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.