BIZTRAC BETA
COMPANY REGISTER PROFILE
994220950 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

SELLÆG AS

Org. no. 994220950 Limited company (AS) Drammen Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −499,000
Equity NOK 4.2m
Incorporated 2009
Share capital NOK 100,000

Signals

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

SELLÆG AS is registered as a limited company in Drammen, Buskerud with organisation number 994220950. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forvaltning, drift, kjøp og salg av kulturhistorisk eiendom, og formidling av kunnskap om bygningsarven.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −499,000 in operating profit.

Former names: CAPPELENGÅRDEN AS

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −499,000
Equity
NOK 4.2m
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
7.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
67.4%
Very good
Equity as a share of total capital

Who owns SELLÆG AS?

JO SELLÆG
SELLÆG AS
NOK 3,000 rev. · NOK −499,000 profit

SELLÆG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SELLÆG AS

Who owns SELLÆG AS?

JO SELLÆG is the largest registered owner, with 51.0%.

What is the revenue of SELLÆG AS?

SELLÆG AS had revenue of NOK 3,000 in 2025.

Who is the general manager of SELLÆG AS?

Jo Sellæg is registered as general manager of SELLÆG AS.

Where is SELLÆG AS based?

SELLÆG AS has its business address in Drammen.

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.