BIZTRAC BETA
Collection of non-hazardous waste

EASYAVFALL AS

Org. no. 927266113 Limited company (AS) Nittedal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 17.5m
Operating profit NOK 2.9m
Equity NOK 2.7m
Incorporated 2021
Employees 5
Share capital NOK 100,000

EASYAVFALL AS is registered as a limited company in Nittedal, Akershus with organisation number 927266113. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drifte innsamling av avfall med avfallstransport, utføre renhold av bygninger og interiør, vaktmestertjenester samt tilby noe godstransport på vei og andre produkter/tjenester som naturlig hører sammen med dette. Samt eie og drive annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.5m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 17.5m
Operating profit
NOK 2.9m
Equity
NOK 2.7m
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns EASYAVFALL AS?

BØTTGERS AS
EASYAVFALL AS
NOK 17.5m rev. · NOK 2.9m profit

EASYAVFALL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EASYAVFALL AS

Who owns EASYAVFALL AS?

BØTTGERS AS is the largest registered owner, with 60.0%.

What is the revenue of EASYAVFALL AS?

EASYAVFALL AS had revenue of NOK 17.5m in 2024.

Who is the general manager of EASYAVFALL AS?

Robin Bøttger is registered as general manager of EASYAVFALL AS.

Where is EASYAVFALL AS based?

EASYAVFALL AS has its business address in Nittedal.

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.