biztrac. BETA
COMPANY REGISTER PROFILE
936141323 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

KICK LYD OG LYS AS

Org. no. 936141323 Limited company (AS) Kristiansand Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 117,000
Equity NOK 122,000
Incorporated 2025
Share capital NOK 30,000

KICK LYD OG LYS AS is registered as a limited company in Kristiansand, Agder with organisation number 936141323. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av restauranter, bar, scene- og kulturarrangementer eller lignende som naturlig står i forbindelse med dette. Kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 117,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 117,000
Equity
NOK 122,000
Est. value
NOK 529,000

Financial health · 2025

Liquidity
-1.80
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
155.4%
Very good
Equity as a share of total capital

Who owns KICK LYD OG LYS AS?

KICK LYD OG LYS AS
NOK 1.6m rev. · NOK 117,000 profit

KICK LYD OG LYS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KICK LYD OG LYS AS

Who owns KICK LYD OG LYS AS?

Nicoleta Balan is the largest registered owner, with 50.0%.

What is the revenue of KICK LYD OG LYS AS?

KICK LYD OG LYS AS had revenue of NOK 1.6m in 2025.

Who is the general manager of KICK LYD OG LYS AS?

Chriss Trygve Lauritsen is registered as general manager of KICK LYD OG LYS AS.

Where is KICK LYD OG LYS AS based?

KICK LYD OG LYS AS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.