biztrac. BETA
COMPANY REGISTER PROFILE
984992637 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of other technical ceramic products

CERAM TOOLS AS

Org. no. 984992637 Limited company (AS) Kristiansand Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 589,000
Incorporated 2002
Share capital NOK 100,000

CERAM TOOLS AS is registered as a limited company in Kristiansand, Agder with organisation number 984992637. The business is classified under manufacture of other technical ceramic products (NACE 23.440). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikle, produsere og omsette keramiske komponenter, og kunne drive med enhver annen beslektet virksomhet, herunder deltagelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK 0
▲ +100 %
Equity
NOK 589,000
▲ +88 %
Est. value
NOK 693,000

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
34.9%
Good
Equity as a share of total capital

Who owns CERAM TOOLS AS?

CERAM TOOLS AS
NOK 0 rev. · NOK 0 profit

CERAM TOOLS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CERAM TOOLS AS

Who owns CERAM TOOLS AS?

Harald Schjelderup is the largest registered owner, with 100.0%.

What is the revenue of CERAM TOOLS AS?

CERAM TOOLS AS had revenue of NOK 0 in 2025.

Who is the general manager of CERAM TOOLS AS?

Harald Schjelderup is registered as general manager of CERAM TOOLS AS.

Where is CERAM TOOLS AS based?

CERAM TOOLS AS has its business address in Tveit.

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.