BIZTRAC BETA
Wholesale of household, office and shop furniture, carpets and lighting equipment

LIVV AS

Org. no. 917399387 Limited company (AS) Asker Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 16.1m
Operating profit NOK 407,000
Equity NOK 416,000
Incorporated 2016
Share capital NOK 100,000

LIVV AS is registered as a limited company in Asker, Akershus with organisation number 917399387. The business is classified under wholesale of household, office and shop furniture, carpets and lighting equipment (NACE 46.470). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av møbler, belysning, tekstiler, baderomstilbehør samt gjesteprodukter til hoteller, samt leveranse og komplette installasjoner av prosjekter innenfor det offentlige miljø som hoteller, restauranter, møterom. etc., samt virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.1m in revenue and NOK 407,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.1m
Operating profit
NOK 407,000
Equity
NOK 416,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Satisfactory
Equity as a share of total capital

Who owns LIVV AS?

LIVV AB
LIVV AS
NOK 16.1m rev. · NOK 407,000 profit

LIVV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIVV AS

Who owns LIVV AS?

LIVV AB is the largest registered owner, with 100.0%.

What is the revenue of LIVV AS?

LIVV AS had revenue of NOK 16.1m in 2025.

Who is the general manager of LIVV AS?

Hans-Fredrik Rundblom is registered as general manager of LIVV AS.

Where is LIVV AS based?

LIVV AS has its business address in Billingstad.

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.