biztrac. BETA
COMPANY REGISTER PROFILE
930842532 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
All other professional, scientific and technical activities n.e.c.

OR-TAKST AS

Org. no. 930842532 Limited company (AS) Ullensaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK 4,000
Equity NOK −10,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10k kr).

OR-TAKST AS is registered as a limited company in Ullensaker, Akershus with organisation number 930842532. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Takst av eiendom og skader.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK 4,000
Equity
NOK −10,000
▲ +27 %

Financial health · 2025

Liquidity
14.19
Very good
Current assets ÷ current liabilities
Profitability
28.6%
Very good
Return on total assets
Solidity
-64.5%
Weak
Equity as a share of total capital

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

Who owns OR-TAKST AS?

OR-TAKST AS
NOK 5,000 rev. · NOK 4,000 profit

OR-TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OR-TAKST AS

Who owns OR-TAKST AS?

ØYSTEIN RUSTAD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OR-TAKST AS?

OR-TAKST AS had revenue of NOK 5,000 in 2025.

Who is the general manager of OR-TAKST AS?

Øystein Rustad is registered as general manager of OR-TAKST AS.

Where is OR-TAKST AS based?

OR-TAKST AS has its business address in Jessheim.

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.