BIZTRAC BETA
Accounting and bookkeeping

ØKORÅD BAMBLE AS

Org. no. 821551692 Limited company (AS) Bamble Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 10.6m
Operating profit NOK 684,000
Equity NOK 1.6m
Incorporated 2018
Employees 8
Share capital NOK 200,000

ØKORÅD BAMBLE AS is registered as a limited company in Bamble, Telemark with organisation number 821551692. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018 and has 8 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Regnskapsføring, økonomisk rådgivning og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.6m in revenue and NOK 684,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.6m
Operating profit
NOK 684,000
Equity
NOK 1.6m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns ØKORÅD BAMBLE AS?

HEIDI TANGVALD
ØKORÅD BAMBLE AS
NOK 10.6m rev. · NOK 684,000 profit

ØKORÅD BAMBLE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ØKORÅD BAMBLE AS own?

ØKORÅD BAMBLE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØKORÅD BAMBLE AS

Who owns ØKORÅD BAMBLE AS?

HEIDI TANGVALD is the largest registered owner, with 25.0%.

What is the revenue of ØKORÅD BAMBLE AS?

ØKORÅD BAMBLE AS had revenue of NOK 10.6m in 2024.

Who is the general manager of ØKORÅD BAMBLE AS?

Svein Inge Nyhus is registered as general manager of ØKORÅD BAMBLE AS.

Where is ØKORÅD BAMBLE AS based?

ØKORÅD BAMBLE AS has its business address in Stathelle.

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.