BIZTRAC BETA
Development of building projects

WORKINNTOPPEN AS

Org. no. 911667487 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 677,000
Operating profit NOK −116,000
Equity NOK 290,000
Incorporated 2013
Share capital NOK 100,000

Signals

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

WORKINNTOPPEN AS is registered as a limited company in Oslo, Oslo with organisation number 911667487. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverve, utvikle, drive og avhende fast eiendom, samt all annen naturlig tilhørende virksomhet. Selskapet kan eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 677,000 in revenue and NOK −116,000 in operating profit.

Key figures · 2025

Revenue
NOK 677,000
Operating profit
NOK −116,000
Equity
NOK 290,000
Est. value
NOK 754,000

Financial health · 2025

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

Who owns WORKINNTOPPEN AS?

BARLINDHAUG EIENDOM AS
WORKINNTOPPEN AS
NOK 677,000 rev. · NOK −116,000 profit

WORKINNTOPPEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WORKINNTOPPEN AS

Who owns WORKINNTOPPEN AS?

BARLINDHAUG EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of WORKINNTOPPEN AS?

WORKINNTOPPEN AS had revenue of NOK 677,000 in 2025.

Who is the general manager of WORKINNTOPPEN AS?

Lasse Lundhaug is registered as general manager of WORKINNTOPPEN AS.

Where is WORKINNTOPPEN AS based?

WORKINNTOPPEN 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.