BIZTRAC BETA
Business and other management consultancy activities

RESTH AS

Org. no. 930183016 Limited company (AS) Lier Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 293,000
Operating profit NOK 276,000
Equity NOK 746,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-07 Aksjekapital registrert 2026-07-07.

RESTH AS is registered as a limited company in Lier, Buskerud with organisation number 930183016. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og/eller andeler i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 293,000 in revenue and NOK 276,000 in operating profit.

Key figures · 2025

Revenue
NOK 293,000
Operating profit
NOK 276,000
Equity
NOK 746,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns RESTH AS?

THERESE SOFIE KINAL
RESTH AS
NOK 293,000 rev. · NOK 276,000 profit

RESTH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RESTH AS own?

RESTH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RESTH AS

Who owns RESTH AS?

THERESE SOFIE KINAL is the largest registered owner, with 100.0%.

What is the revenue of RESTH AS?

RESTH AS had revenue of NOK 293,000 in 2025.

Who is the general manager of RESTH AS?

Therese Sofie Kinal is registered as general manager of RESTH AS.

Where is RESTH AS based?

RESTH AS has its business address in Sylling.

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.