BIZTRAC BETA
COMPANY REGISTER PROFILE
992652861 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ÅSVEIEN 6B AS

Org. no. 992652861 Limited company (AS) Asker Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 208,000
Incorporated 2008
Share capital NOK 284,000

Signals

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

ÅSVEIEN 6B AS is registered as a limited company in Asker, Akershus with organisation number 992652861. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 284,000, divided into 284433 shares. The company's stated purpose is: “Drift og investering i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −5,000
▲ +27 %
Equity
NOK 208,000
▼ −2 %
Est. value
NOK 189,000

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
84.9%
Very good
Equity as a share of total capital

Who owns ÅSVEIEN 6B AS?

ÅSVEIEN 6B AS
· NOK −5,000 profit

ÅSVEIEN 6B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅSVEIEN 6B AS

Who owns ÅSVEIEN 6B AS?

SJOBEGO AS is the largest registered owner, with 100.0%.

Where is ÅSVEIEN 6B AS based?

ÅSVEIEN 6B AS has its business address in Sætre.

Property

Business address Åsveien 6B, 3475 Sætre
Cadastral unit 3203-301/586/0/0

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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