biztrac. BETA
COMPANY REGISTER PROFILE
935596912 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠MILJØ SEKKEN AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Materials recovery

MILJØ SEKKEN AS

Org. no. 935596912 Limited company (AS) Aurskog-Høland Incorporated 2025 In liquidation
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 16,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

MILJØ SEKKEN AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 935596912. The business is classified under materials recovery (NACE 38.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Levering av gjenvinnings- og miljøtjenester. Tjenestetilbudet omfatter avfallshåndtering, metallgjenvinning, industriservice, farlig avfall, nedstrømsløsninger, riving, miljøsanering og hva som ellers står i forbindelse med disse virksomhetsområder.”.

Former names: ISEKK AS

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 16,000

Financial health · 2025

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

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

Who owns MILJØ SEKKEN AS?

MILJØ SEKKEN AS
· NOK −4,000 profit

MILJØ SEKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILJØ SEKKEN AS

Who owns MILJØ SEKKEN AS?

Tonni Erik Jacobsen is the largest registered owner, with 100.0%.

Where is MILJØ SEKKEN AS based?

MILJØ SEKKEN AS has its business address in Bjørkelangen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.