BIZTRAC BETA
Repair and maintenance of household appliances and home and garden equipment

K. DEVIK AS

Org. no. 929934709 Limited company (AS) Namsos Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 443,000
Operating profit NOK 77,000
Equity NOK 56,000
Incorporated 2022
Share capital NOK 40,000

K. DEVIK AS is registered as a limited company in Namsos, Trøndelag with organisation number 929934709. The business is classified under repair and maintenance of household appliances and home and garden equipment (NACE 95.220). The company was incorporated in 2022. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Reparasjoner og service på symaskiner. Selskapet skal også kunne engasjere seg i annen økonomisk virksomhet som styret til enhver tid finner økonomisk forsvarlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 443,000 in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 443,000
Operating profit
NOK 77,000
Equity
NOK 56,000
Est. value
NOK 297,000

Financial health · 2025

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.5%
Weak
Equity as a share of total capital

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

Who owns K. DEVIK AS?

KNUT ARNE DEVIK
K. DEVIK AS
NOK 443,000 rev. · NOK 77,000 profit

K. DEVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K. DEVIK AS

Who owns K. DEVIK AS?

KNUT ARNE DEVIK is the largest registered owner, with 100.0%.

What is the revenue of K. DEVIK AS?

K. DEVIK AS had revenue of NOK 443,000 in 2025.

Who is the general manager of K. DEVIK AS?

Knut Arne Devik is registered as general manager of K. DEVIK AS.

Where is K. DEVIK AS based?

K. DEVIK AS has its business address in Namsos.

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.