BIZTRAC BETA
Photographic activities

STEADY CATCH AS

Org. no. 927064170 Limited company (AS) Porsgrunn Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 29,000
Operating profit NOK −28,000
Equity NOK −11,000
Incorporated 2021
Share capital NOK 45,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).

STEADY CATCH AS is registered as a limited company in Porsgrunn, Telemark with organisation number 927064170. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2021. Registered share capital is NOK 45,000, divided into 45000 shares. The company's stated purpose is: “Filming og fotografering, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 29,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 29,000
Operating profit
NOK −28,000
Equity
NOK −11,000

Financial health · 2024

Liquidity
19.75
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-33.7%
Weak
Equity as a share of total capital

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

Who owns STEADY CATCH AS?

JAN KENNETH EVANGER
STEADY CATCH AS
NOK 29,000 rev. · NOK −28,000 profit

STEADY CATCH AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEADY CATCH AS

Who owns STEADY CATCH AS?

JAN KENNETH EVANGER is the largest registered owner, with 66.7%.

What is the revenue of STEADY CATCH AS?

STEADY CATCH AS had revenue of NOK 29,000 in 2024.

Who is the general manager of STEADY CATCH AS?

Jan Kenneth Evanger is registered as general manager of STEADY CATCH AS.

Where is STEADY CATCH AS based?

STEADY CATCH AS has its business address in Porsgrunn.

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.