biztrac. BETA
COMPANY REGISTER PROFILE
932018292 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

AVLØPS-PROSJEKTERING AS

Org. no. 932018292 Limited company (AS) Indre Østfold Incorporated 2023 Active
Revenue 2025 NOK 104,000
Operating profit NOK −26,000
Equity NOK 43,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

AVLØPS-PROSJEKTERING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 932018292. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Prosjektering av avløpsanlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 104,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 104,000
▼ −63 %
Operating profit
NOK −26,000
▼ −156 %
Equity
NOK 43,000
▼ −32 %
Est. value
NOK 37,000

Financial health · 2025

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

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

Who owns AVLØPS-PROSJEKTERING AS?

AVLØPS-PROSJEKTERING AS
NOK 104,000 rev. · NOK −26,000 profit

AVLØPS-PROSJEKTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AVLØPS-PROSJEKTERING AS

Who owns AVLØPS-PROSJEKTERING AS?

Ole-Martin Berserker Lillevold is the largest registered owner, with 100.0%.

What is the revenue of AVLØPS-PROSJEKTERING AS?

AVLØPS-PROSJEKTERING AS had revenue of NOK 104,000 in 2025.

Where is AVLØPS-PROSJEKTERING AS based?

AVLØPS-PROSJEKTERING AS has its business address in Askim.

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.