BIZTRAC BETA
COMPANY REGISTER PROFILE
871040672 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

WAAGES REGNSKAPSKONTOR

Org. no. 871040672 Sole proprietorship (ENK) Bodø Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.4m
Equity NOK 890,000

WAAGES REGNSKAPSKONTOR is registered as a sole proprietorship in Bodø, Nordland with organisation number 871040672. The business is classified under accounting and bookkeeping (NACE 69.202). The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.4m
Equity
NOK 890,000
Est. value
NOK 5.2m

Financial health · 2024

Liquidity
10.64
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
90.9%
Very good
Equity as a share of total capital

Who owns WAAGES REGNSKAPSKONTOR?

No shareholders are registered for WAAGES REGNSKAPSKONTOR in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about WAAGES REGNSKAPSKONTOR

What is the revenue of WAAGES REGNSKAPSKONTOR?

WAAGES REGNSKAPSKONTOR had revenue of NOK 1.8m in 2024.

Who is the general manager of WAAGES REGNSKAPSKONTOR?

Robert Waage is registered as general manager of WAAGES REGNSKAPSKONTOR.

Where is WAAGES REGNSKAPSKONTOR based?

WAAGES REGNSKAPSKONTOR has its business address in Bodø.

Property

Business address Haugstuveien 17, 8010 Bodø
Cadastral unit 1804-31/1518/0/0
Building Andre småhus med 3 boliger eller flere · 3 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.