BIZTRAC BETA
Other tour operator activities

BRUSE INVEST AS

Org. no. 979888279 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK 20,000
Equity NOK −5,000
Incorporated 1997
Share capital NOK 150,000

Signals

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

BRUSE INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 979888279. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 1997. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, aksjer, annen forretningsvirksomhet etc., samt konsulentvirksomhet og hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK 20,000
Equity
NOK −5,000
Est. value
NOK 93,000

Financial health · 2025

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

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

Who owns BRUSE INVEST AS?

JAN BRUSERUD
BRUSE INVEST AS
NOK 20,000 rev. · NOK 20,000 profit

BRUSE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRUSE INVEST AS

Who owns BRUSE INVEST AS?

JAN BRUSERUD is the largest registered owner, with 100.0%.

What is the revenue of BRUSE INVEST AS?

BRUSE INVEST AS had revenue of NOK 20,000 in 2025.

Who is the general manager of BRUSE INVEST AS?

Jan Bruserud is registered as general manager of BRUSE INVEST AS.

Where is BRUSE INVEST AS based?

BRUSE INVEST AS has its business address in Oslo.

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.