biztrac. BETA
COMPANY REGISTER PROFILE
930082023 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

KLEPPESTØ BOLIG AS

Org. no. 930082023 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 253,000
Operating profit NOK 151,000
Equity NOK 858,000
Incorporated 2022
Share capital NOK 1.0m

KLEPPESTØ BOLIG AS is registered as a limited company in Øygarden, Vestland with organisation number 930082023. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Eie å forvalte eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 253,000 in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 253,000
▲ +1 %
Operating profit
NOK 151,000
▲ +16 %
Equity
NOK 858,000
▼ −2 %
Est. value
NOK 801,000

Financial health · 2025

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
3.8%
Weak
Return on total assets
Solidity
20.6%
Good
Equity as a share of total capital

Who owns KLEPPESTØ BOLIG AS?

KLEPPESTØ BOLIG AS
NOK 253,000 rev. · NOK 151,000 profit

KLEPPESTØ BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEPPESTØ BOLIG AS

Who owns KLEPPESTØ BOLIG AS?

CHRISTER KLEPPESTØ AS is the largest registered owner, with 100.0%.

What is the revenue of KLEPPESTØ BOLIG AS?

KLEPPESTØ BOLIG AS had revenue of NOK 253,000 in 2025.

Who is the general manager of KLEPPESTØ BOLIG AS?

Christer-Andre Kleppestø is registered as general manager of KLEPPESTØ BOLIG AS.

Where is KLEPPESTØ BOLIG AS based?

KLEPPESTØ BOLIG AS has its business address in Rong.

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.