BIZTRAC BETA
Painting and glazing

JK MALING OG RENHOLD AS

Org. no. 817300472 Limited company (AS) Randaberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 663,000
Operating profit NOK −110,000
Equity NOK 112,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−110k kr).

JK MALING OG RENHOLD AS is registered as a limited company in Randaberg, Rogaland with organisation number 817300472. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Maling og vedlikeholdsarbeid samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 663,000 in revenue and NOK −110,000 in operating profit.

Key figures · 2025

Revenue
NOK 663,000
Operating profit
NOK −110,000
Equity
NOK 112,000
Est. value
NOK 279,000

Financial health · 2025

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

Who owns JK MALING OG RENHOLD AS?

JANUSZ ORLOWSKI
JK MALING OG RENHOLD AS
NOK 663,000 rev. · NOK −110,000 profit

JK MALING OG RENHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JK MALING OG RENHOLD AS

Who owns JK MALING OG RENHOLD AS?

JANUSZ ORLOWSKI is the largest registered owner, with 100.0%.

What is the revenue of JK MALING OG RENHOLD AS?

JK MALING OG RENHOLD AS had revenue of NOK 663,000 in 2025.

Who is the general manager of JK MALING OG RENHOLD AS?

Janusz Orlowski is registered as general manager of JK MALING OG RENHOLD AS.

Where is JK MALING OG RENHOLD AS based?

JK MALING OG RENHOLD AS has its business address in Randaberg.

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.