BIZTRAC BETA
Uoppgitt

KLEKKENSVINGEN AS

Org. no. 829546132 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 6.0m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLEKKENSVINGEN AS is registered as a limited company in Oslo, Oslo with organisation number 829546132. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignede virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 6.0m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns KLEKKENSVINGEN AS?

TRONRUD AS
KLEKKENSVINGEN AS
NOK 0 rev. · NOK −13,000 profit

KLEKKENSVINGEN AS has 2 registered shareholders:

All shareholders and roles →

Group structure

KLEKKENSVINGEN AS er morselskap for 31 datterselskaper:

Frequently asked questions about KLEKKENSVINGEN AS

Who owns KLEKKENSVINGEN AS?

TRONRUD AS is the largest registered owner, with 68.7%.

What is the revenue of KLEKKENSVINGEN AS?

KLEKKENSVINGEN AS had revenue of NOK 0 in 2025.

Where is KLEKKENSVINGEN AS based?

KLEKKENSVINGEN 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.