BIZTRAC BETA
Other specialised construction activities in construction of buildings

KJELVIK MUR OG BETONG AS

Org. no. 931814826 Limited company (AS) Steinkjer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 14,000
Equity NOK 109,000
Incorporated 2023
Share capital NOK 30,000

KJELVIK MUR OG BETONG AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 931814826. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Mur, flis, betong og annen entreprenørvirksomhet. Samt utleie av arbeidskraft.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 14,000
Equity
NOK 109,000
Est. value
NOK 82,000

Financial health · 2024

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

Who owns KJELVIK MUR OG BETONG AS?

KRISTOFFER KJELVIK
KJELVIK MUR OG BETONG AS
NOK 1.3m rev. · NOK 14,000 profit

KJELVIK MUR OG BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJELVIK MUR OG BETONG AS

Who owns KJELVIK MUR OG BETONG AS?

KRISTOFFER KJELVIK is the largest registered owner, with 100.0%.

What is the revenue of KJELVIK MUR OG BETONG AS?

KJELVIK MUR OG BETONG AS had revenue of NOK 1.3m in 2024.

Who is the general manager of KJELVIK MUR OG BETONG AS?

Kristoffer Kjelvik is registered as general manager of KJELVIK MUR OG BETONG AS.

Where is KJELVIK MUR OG BETONG AS based?

KJELVIK MUR OG BETONG AS has its business address in Steinkjer.

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.