biztrac. BETA
COMPANY REGISTER PROFILE
989308076 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

MIDTNORSK LAKK & KAROSSERI AS

Org. no. 989308076 Limited company (AS) Steinkjer Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 260,000
Equity NOK 613,000
Incorporated 2006
Share capital NOK 100,000

MIDTNORSK LAKK & KAROSSERI AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 989308076. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Karosseriarbeid og lakkering av motoriserte kjøretøyer samt annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 260,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +93 %
Operating profit
NOK 260,000
▼ −32 %
Equity
NOK 613,000
▲ +74 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
2.05
Very good
Current assets ÷ current liabilities
Profitability
26.3%
Very good
Return on total assets
Solidity
57.1%
Very good
Equity as a share of total capital

Who owns MIDTNORSK LAKK & KAROSSERI AS?

MIDTNORSK LAKK & KAROSSERI AS
NOK 1.9m rev. · NOK 260,000 profit

MIDTNORSK LAKK & KAROSSERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTNORSK LAKK & KAROSSERI AS

Who owns MIDTNORSK LAKK & KAROSSERI AS?

Jan Rune Rønning is the largest registered owner, with 100.0%.

What is the revenue of MIDTNORSK LAKK & KAROSSERI AS?

MIDTNORSK LAKK & KAROSSERI AS had revenue of NOK 1.9m in 2025.

Where is MIDTNORSK LAKK & KAROSSERI AS based?

MIDTNORSK LAKK & KAROSSERI AS has its business address in Sparbu.

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.