BIZTRAC BETA
Site preparation

KLEPPE MULTISERVICE AS

Org. no. 929719611 Limited company (AS) Gloppen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 157,000
Equity NOK 432,000
Incorporated 2022
Share capital NOK 30,000

KLEPPE MULTISERVICE AS is registered as a limited company in Gloppen, Vestland with organisation number 929719611. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen bygg og anlegg, utleige av arbeidskraft og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 157,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 157,000
Equity
NOK 432,000
Est. value
NOK 720,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.0%
Good
Equity as a share of total capital

Who owns KLEPPE MULTISERVICE AS?

AET KLEPPE AS
KLEPPE MULTISERVICE AS
NOK 4.6m rev. · NOK 157,000 profit

KLEPPE MULTISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEPPE MULTISERVICE AS

Who owns KLEPPE MULTISERVICE AS?

AET KLEPPE AS is the largest registered owner, with 100.0%.

What is the revenue of KLEPPE MULTISERVICE AS?

KLEPPE MULTISERVICE AS had revenue of NOK 4.6m in 2025.

Who is the general manager of KLEPPE MULTISERVICE AS?

Runar Stensaker Kleppe is registered as general manager of KLEPPE MULTISERVICE AS.

Where is KLEPPE MULTISERVICE AS based?

KLEPPE MULTISERVICE AS has its business address in Byrkjelo.

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.