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

HARTO REGNSKAPSRÅDGIVNING

Org. no. 999140386 Sole proprietorship (ENK) Bærum Active
Ownership graph ↗
Revenue 2025 NOK 134,000
Operating profit NOK 106,000
Equity NOK 10,000

HARTO REGNSKAPSRÅDGIVNING is registered as a sole proprietorship in Bærum, Akershus with organisation number 999140386. The business is classified under accounting and bookkeeping (NACE 69.202). The most recent filed accounts, for the 2025 financial year, show NOK 134,000 in revenue and NOK 106,000 in operating profit.

Key figures · 2025

Revenue
NOK 134,000
Operating profit
NOK 106,000
Equity
NOK 10,000
Est. value
NOK 341,000

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.0%
Weak
Equity as a share of total capital

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

Who owns HARTO REGNSKAPSRÅDGIVNING?

No shareholders are registered for HARTO REGNSKAPSRÅDGIVNING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HARTO REGNSKAPSRÅDGIVNING

What is the revenue of HARTO REGNSKAPSRÅDGIVNING?

HARTO REGNSKAPSRÅDGIVNING had revenue of NOK 134,000 in 2025.

Where is HARTO REGNSKAPSRÅDGIVNING based?

HARTO REGNSKAPSRÅDGIVNING has its business address in Bekkestua.

Property

Business address Falkeveien 30, 1357 Bekkestua
Cadastral unit 3201-19/683/0/0
Building Kjede/atriumhus · 1 unit

5 companies are registered at this address.

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.