biztrac. BETA
COMPANY REGISTER PROFILE
960283171 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Retail sale of watches and jewellery

KLEIVELAND AS

Org. no. 960283171 Limited company (AS) Bergen Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 12.3m
Operating profit NOK 972,000
Equity NOK 4.0m
Incorporated 1991
Employees 14
Share capital NOK 200,000

KLEIVELAND AS is registered as a limited company in Bergen, Vestland with organisation number 960283171. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1991 and has 14 registered employees. Registered share capital is NOK 200,000, divided into 50 shares. The company's stated purpose is: “Handel, samarbeide med andre virksomheter i enhver form, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.3m in revenue and NOK 972,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.3m
▲ +5 %
Operating profit
NOK 972,000
▼ −12 %
Equity
NOK 4.0m
▼ −3 %
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
2.28
Very good
Current assets ÷ current liabilities
Profitability
14.3%
Good
Return on total assets
Solidity
56.2%
Very good
Equity as a share of total capital

Who owns KLEIVELAND AS?

KLEIVELAND AS
NOK 12.3m rev. · NOK 972,000 profit

KLEIVELAND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLEIVELAND AS

Who owns KLEIVELAND AS?

Merethe Elisabeth Erstad Reigstad is the largest registered owner, with 90.0%.

What is the revenue of KLEIVELAND AS?

KLEIVELAND AS had revenue of NOK 12.3m in 2025.

Who is the general manager of KLEIVELAND AS?

Merethe Elisabeth Erstad Reigstad is registered as general manager of KLEIVELAND AS.

Where is KLEIVELAND AS based?

KLEIVELAND AS has its business address in Indre Arna.

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.