BIZTRAC BETA
Sports and recreation education

KITESURFING.NO AS

Org. no. 926612948 Limited company (AS) Klepp Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 138,000
Operating profit NOK −54,000
Equity NOK 11,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

KITESURFING.NO AS is registered as a limited company in Klepp, Rogaland with organisation number 926612948. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kurs og opplæring innen kitesurfing, samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 138,000 in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 138,000
Operating profit
NOK −54,000
Equity
NOK 11,000
Est. value
NOK 126,000

Financial health · 2025

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

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

Who owns KITESURFING.NO AS?

MARTIN SALEM
KITESURFING.NO AS
NOK 138,000 rev. · NOK −54,000 profit

KITESURFING.NO AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KITESURFING.NO AS

Who owns KITESURFING.NO AS?

MARTIN SALEM is the largest registered owner, with 80.0%.

What is the revenue of KITESURFING.NO AS?

KITESURFING.NO AS had revenue of NOK 138,000 in 2025.

Who is the general manager of KITESURFING.NO AS?

Martin Salem is registered as general manager of KITESURFING.NO AS.

Where is KITESURFING.NO AS based?

KITESURFING.NO AS has its business address in Kleppe.

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.