BIZTRAC BETA
Collection of non-hazardous waste

RUNES CONTAINERSERVICE AS

Org. no. 980438740 Limited company (AS) Aurskog-Høland Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 10.4m
Operating profit NOK 487,000
Equity NOK 996,000
Incorporated 1998
Employees 7
Share capital NOK 600,000

RUNES CONTAINERSERVICE AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 980438740. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 1998 and has 7 registered employees. Registered share capital is NOK 600,000, divided into 6000 shares. The company's stated purpose is: “Transport og avfallssortering, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.4m in revenue and NOK 487,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.4m
Operating profit
NOK 487,000
Equity
NOK 996,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.0%
Satisfactory
Equity as a share of total capital

Who owns RUNES CONTAINERSERVICE AS?

RUNE JOHAN NADDEN
RUNES CONTAINERSERVICE AS
NOK 10.4m rev. · NOK 487,000 profit

RUNES CONTAINERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RUNES CONTAINERSERVICE AS

Who owns RUNES CONTAINERSERVICE AS?

RUNE JOHAN NADDEN is the largest registered owner, with 66.7%.

What is the revenue of RUNES CONTAINERSERVICE AS?

RUNES CONTAINERSERVICE AS had revenue of NOK 10.4m in 2025.

Who is the general manager of RUNES CONTAINERSERVICE AS?

Runar Nyjordet Nadden is registered as general manager of RUNES CONTAINERSERVICE AS.

Where is RUNES CONTAINERSERVICE AS based?

RUNES CONTAINERSERVICE AS has its business address in Løken.

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.