BIZTRAC BETA
Uoppgitt

KLANG AS

Org. no. 933470938 Limited company (AS) Stranda Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 12,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KLANG AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 933470938. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 12,000
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns KLANG AS?

KARL KRISTIAN LANGELAND
KLANG AS
NOK 0 rev. · NOK −11,000 profit

KLANG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLANG AS

Who owns KLANG AS?

KARL KRISTIAN LANGELAND is the largest registered owner, with 100.0%.

What is the revenue of KLANG AS?

KLANG AS had revenue of NOK 0 in 2025.

Who is the general manager of KLANG AS?

Karl Kristian Langeland is registered as general manager of KLANG AS.

Where is KLANG AS based?

KLANG AS has its business address in Hellesylt.

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.