biztrac. BETA
COMPANY REGISTER PROFILE
935608058 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of machinery

ORKER AS

Org. no. 935608058 Limited company (AS) Trondheim Incorporated 2025 Active
Revenue 2025 NOK 152,000
Operating profit NOK 53,000
Equity NOK 64,000
Incorporated 2025
Share capital NOK 30,000

ORKER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935608058. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby reparasjon og vedlikehold av maskiner til landbruk, skogbruk, bygg- og anlegg og industri ellers, inkludert, men ikke begrenset til, feilsøking, reparasjon, delutskifting, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 152,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 152,000
Operating profit
NOK 53,000
Equity
NOK 64,000
Est. value
NOK 204,000

Financial health · 2025

Liquidity
4.04
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
75.3%
Weak
Equity as a share of total capital

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

Who owns ORKER AS?

ORKER AS
NOK 152,000 rev. · NOK 53,000 profit

ORKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ORKER AS

Who owns ORKER AS?

Odd Roar Klæt is the largest registered owner, with 50.0%.

What is the revenue of ORKER AS?

ORKER AS had revenue of NOK 152,000 in 2025.

Who is the general manager of ORKER AS?

Odd Roar Klæt is registered as general manager of ORKER AS.

Where is ORKER AS based?

ORKER AS has its business address in Leinstrand.

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.