BIZTRAC BETA
Combined facilities support activities

TORJUS BUVARP AS

Org. no. 936706673 Limited company (AS) Lørenskog Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 6,000
Operating profit NOK −11,000
Equity NOK 12,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−11k kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-11-14.

TORJUS BUVARP AS is registered as a limited company in Lørenskog, Akershus with organisation number 936706673. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av varer og tjenester inkludert håndverk, kunst, digital drift, kommisjonssalg og investering.”.

Key figures

Revenue
NOK 6,000
Operating profit
NOK −11,000
Equity
NOK 12,000
Est. value
NOK 10,000

Financial health · 2025

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

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

Who owns TORJUS BUVARP AS?

TORJUS BUVARP
TORJUS BUVARP AS
NOK 6,000 rev. · NOK −11,000 profit

TORJUS BUVARP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORJUS BUVARP AS

Who owns TORJUS BUVARP AS?

TORJUS BUVARP is the largest registered owner, with 100.0%.

What is the revenue of TORJUS BUVARP AS?

TORJUS BUVARP AS had revenue of NOK 6,000.

Who is the general manager of TORJUS BUVARP AS?

Torjus Buvarp is registered as general manager of TORJUS BUVARP AS.

Where is TORJUS BUVARP AS based?

TORJUS BUVARP AS has its business address in Lørenskog.

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.