BIZTRAC BETA
Buying and selling of own real estate

SØRBØ KLEPPE AS

Org. no. 982951798 Limited company (AS) Time Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK −1.3m
Incorporated 2001
Share capital NOK 400,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

SØRBØ KLEPPE AS is registered as a limited company in Time, Rogaland with organisation number 982951798. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2001. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Kjøp og salg av tomter/eiendommer til boligformål, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −1.3m

Financial health · 2024

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

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

Who owns SØRBØ KLEPPE AS?

FAUNE AS
SØRBØ KLEPPE AS
NOK 0 rev. · NOK −12,000 profit

SØRBØ KLEPPE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRBØ KLEPPE AS

Who owns SØRBØ KLEPPE AS?

FAUNE AS is the largest registered owner, with 56.5%.

What is the revenue of SØRBØ KLEPPE AS?

SØRBØ KLEPPE AS had revenue of NOK 0 in 2025.

Who is the general manager of SØRBØ KLEPPE AS?

Jan Arvid Nese is registered as general manager of SØRBØ KLEPPE AS.

Where is SØRBØ KLEPPE AS based?

SØRBØ KLEPPE AS has its business address in Bryne.

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.