BIZTRAC BETA
COMPANY REGISTER PROFILE
979521294 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Other services incidental to land transport n.e.c.

RENA BILBERGING Stein Håvard Andraa

Org. no. 979521294 Sole proprietorship (ENK) Åmot Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 1.4m
Equity NOK 1.5m

RENA BILBERGING Stein Håvard Andraa is registered as a sole proprietorship in Åmot, Innlandet with organisation number 979521294. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 1.4m
Equity
NOK 1.5m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns RENA BILBERGING Stein Håvard Andraa?

No shareholders are registered for RENA BILBERGING Stein Håvard Andraa in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about RENA BILBERGING Stein Håvard Andraa

What is the revenue of RENA BILBERGING Stein Håvard Andraa?

RENA BILBERGING Stein Håvard Andraa had revenue of NOK 7.5m in 2024.

Where is RENA BILBERGING Stein Håvard Andraa based?

RENA BILBERGING Stein Håvard Andraa has its business address in Rena.

Property

Business address Hovdmoveien 8, 2450 Rena
Cadastral unit 3422-26/48/0/0
Building Annen industribygning · 5 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.