BIZTRAC BETA
Business and other management consultancy activities

RUTEX AS

Org. no. 928466116 Limited company (AS) Vestby Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 30,000
Equity NOK −433,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

RUTEX AS is registered as a limited company in Vestby, Akershus with organisation number 928466116. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen tekstil innsamling - 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 4.3m in revenue and NOK 30,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 30,000
Equity
NOK −433,000
Est. value
NOK 216,000

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-52.0%
Weak
Equity as a share of total capital

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

Who owns RUTEX AS?

RUNAR HANSEN
RUTEX AS
NOK 4.3m rev. · NOK 30,000 profit

RUTEX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUTEX AS

Who owns RUTEX AS?

RUNAR HANSEN is the largest registered owner, with 100.0%.

What is the revenue of RUTEX AS?

RUTEX AS had revenue of NOK 4.3m in 2025.

Who is the general manager of RUTEX AS?

Runar Hansen is registered as general manager of RUTEX AS.

Where is RUTEX AS based?

RUTEX AS has its business address in Son.

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.