BIZTRAC BETA
Accounting and bookkeeping

REGNSKAPSKONTORET REBUS AS

Org. no. 833950592 Limited company (AS) Nærøysund Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK −214,000
Equity NOK 1.2m
Incorporated 1983
Employees 5
Share capital NOK 102,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−214k kr).

REGNSKAPSKONTORET REBUS AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 833950592. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1983 and has 5 registered employees. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Regnskapskontor.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK −214,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK −214,000
Equity
NOK 1.2m
Est. value
NOK 6.5m

Financial health · 2024

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.5%
Very good
Equity as a share of total capital

Who owns REGNSKAPSKONTORET REBUS AS?

HÅKON BACH
REGNSKAPSKONTORET REBUS AS
NOK 5.7m rev. · NOK −214,000 profit

REGNSKAPSKONTORET REBUS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REGNSKAPSKONTORET REBUS AS

Who owns REGNSKAPSKONTORET REBUS AS?

HÅKON BACH is the largest registered owner, with 50.0%.

What is the revenue of REGNSKAPSKONTORET REBUS AS?

REGNSKAPSKONTORET REBUS AS had revenue of NOK 5.7m in 2024.

Who is the general manager of REGNSKAPSKONTORET REBUS AS?

Håkon Bach is registered as general manager of REGNSKAPSKONTORET REBUS AS.

Where is REGNSKAPSKONTORET REBUS AS based?

REGNSKAPSKONTORET REBUS AS has its business address in Kolvereid.

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.