BIZTRAC BETA
Interior design activities

LK INTERIØRARKITEKTUR AS

Org. no. 921444745 Limited company (AS) Sandefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 12,000
Operating profit NOK −76,000
Equity NOK 75,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−76k kr).

LK INTERIØRARKITEKTUR AS is registered as a limited company in Sandefjord, Vestfold with organisation number 921444745. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av tjenester innen interiørarkitektur, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12,000 in revenue and NOK −76,000 in operating profit.

Key figures · 2025

Revenue
NOK 12,000
Operating profit
NOK −76,000
Equity
NOK 75,000
Est. value
NOK 49,000

Financial health · 2024

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

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

Who owns LK INTERIØRARKITEKTUR AS?

LIGITA KESTERE
LK INTERIØRARKITEKTUR AS
NOK 12,000 rev. · NOK −76,000 profit

LK INTERIØRARKITEKTUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LK INTERIØRARKITEKTUR AS

Who owns LK INTERIØRARKITEKTUR AS?

LIGITA KESTERE is the largest registered owner, with 100.0%.

What is the revenue of LK INTERIØRARKITEKTUR AS?

LK INTERIØRARKITEKTUR AS had revenue of NOK 12,000 in 2025.

Where is LK INTERIØRARKITEKTUR AS based?

LK INTERIØRARKITEKTUR AS has its business address in Sandefjord.

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.