BIZTRAC BETA
Other technical consultancy

WELL MADE AS

Org. no. 828753932 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 140,000
Operating profit NOK −39,000
Equity NOK 27,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−39k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

WELL MADE AS is registered as a limited company in Oslo, Oslo with organisation number 828753932. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av ingeniørtjenester online.”. The most recent filed accounts, for the 2025 financial year, show NOK 140,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 140,000
Operating profit
NOK −39,000
Equity
NOK 27,000
Est. value
NOK 160,000

Financial health · 2025

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

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

Who owns WELL MADE AS?

BJØRKHAGEN AS
WELL MADE AS
NOK 140,000 rev. · NOK −39,000 profit

WELL MADE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WELL MADE AS

Who owns WELL MADE AS?

BJØRKHAGEN AS is the largest registered owner, with 100.0%.

What is the revenue of WELL MADE AS?

WELL MADE AS had revenue of NOK 140,000 in 2025.

Who is the general manager of WELL MADE AS?

Stein Weberg is registered as general manager of WELL MADE AS.

Where is WELL MADE AS based?

WELL MADE AS has its business address in Oslo.

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.