biztrac. BETA
COMPANY REGISTER PROFILE
932478404 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Painting and glazing

TUZAR & SØN AS

Org. no. 932478404 Limited company (AS) Stryn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −105,000
Equity NOK 114,000
Incorporated 2023
Employees 6
Share capital NOK 30,000

Signals

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

TUZAR & SØN AS is registered as a limited company in Stryn, Vestland with organisation number 932478404. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen malerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −105,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +119 %
Operating profit
NOK −105,000
▼ −156 %
Equity
NOK 114,000
▼ −48 %
Est. value
NOK 106,000

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
-25.0%
Not satisfactory
Return on total assets
Solidity
22.2%
Good
Equity as a share of total capital

Who owns TUZAR & SØN AS?

TUZAR & SØN AS
NOK 1.1m rev. · NOK −105,000 profit

TUZAR & SØN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUZAR & SØN AS

Who owns TUZAR & SØN AS?

Jozef Tuzar is the largest registered owner, with 100.0%.

What is the revenue of TUZAR & SØN AS?

TUZAR & SØN AS had revenue of NOK 1.1m in 2025.

Where is TUZAR & SØN AS based?

TUZAR & SØN AS has its business address in Stryn.

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.