BIZTRAC BETA
Retail sale of books

LUSH DIVE AS

Org. no. 915076157 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 1.1m
Equity NOK 1.4m
Incorporated 2015
Share capital NOK 30,000

LUSH DIVE AS is registered as a limited company in Oslo, Oslo with organisation number 915076157. The business is classified under retail sale of books (NACE 47.610). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Handel med Papir/ rekvisita/ småvarehandel / utsalg i butikk og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 1.1m
Equity
NOK 1.4m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns LUSH DIVE AS?

ANDREAS JOHANN LOBBEN SMAALAND
LUSH DIVE AS
NOK 6.9m rev. · NOK 1.1m profit

LUSH DIVE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUSH DIVE AS

Who owns LUSH DIVE AS?

ANDREAS JOHANN LOBBEN SMAALAND is the largest registered owner, with 50.0%.

What is the revenue of LUSH DIVE AS?

LUSH DIVE AS had revenue of NOK 6.9m in 2025.

Who is the general manager of LUSH DIVE AS?

Laila Hjelmeland is registered as general manager of LUSH DIVE AS.

Where is LUSH DIVE AS based?

LUSH DIVE 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.