BIZTRAC BETA
COMPANY REGISTER PROFILE
933556530 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Manufacture of furniture

KETIL KIND TRELAKKERING AS

Org. no. 933556530 Limited company (AS) Ringerike Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 32,000
Equity NOK 45,000
Incorporated 2024
Share capital NOK 30,000

KETIL KIND TRELAKKERING AS is registered as a limited company in Ringerike, Buskerud with organisation number 933556530. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon av møbler, overflatebehandling og alt som faller naturlig under denne næringen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 32,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +20 %
Operating profit
NOK 32,000
▼ −89 %
Equity
NOK 45,000
▼ −43 %
Est. value
NOK 365,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
8.8%
Satisfactory
Return on total assets
Solidity
12.7%
Weak
Equity as a share of total capital

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

Who owns KETIL KIND TRELAKKERING AS?

KETIL KIND TRELAKKERING AS
NOK 1.7m rev. · NOK 32,000 profit

KETIL KIND TRELAKKERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KETIL KIND TRELAKKERING AS

Who owns KETIL KIND TRELAKKERING AS?

KETIL KIND is the largest registered owner, with 100.0%.

What is the revenue of KETIL KIND TRELAKKERING AS?

KETIL KIND TRELAKKERING AS had revenue of NOK 1.7m in 2025.

Where is KETIL KIND TRELAKKERING AS based?

KETIL KIND TRELAKKERING AS has its business address in Tyristrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.