BIZTRAC BETA
Rental and operating of own or leased real estate

ÅS KONTORSENTER AS

Org. no. 948978296 Limited company (AS) Tønsberg Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 20.8m
Operating profit NOK 6.6m
Equity NOK 28.7m
Incorporated 1988
Share capital NOK 3.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅS KONTORSENTER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 948978296. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 3.0m, divided into 30650 shares. The company's stated purpose is: “Utvikling, oppføring av eiendommer, utleievirksomhet, eiendomsforvaltning og annen virksomhet som naturlig faller innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.8m in revenue and NOK 6.6m in operating profit.

Key figures · 2024

Revenue
NOK 20.8m
Operating profit
NOK 6.6m
Equity
NOK 28.7m
Est. value
NOK 28.6m

Financial health · 2024

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.1%
Good
Equity as a share of total capital

Who owns ÅS KONTORSENTER AS?

ÅS NÆRINGSPARK AS
ÅS KONTORSENTER AS
NOK 20.8m rev. · NOK 6.6m profit

ÅS KONTORSENTER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ÅS KONTORSENTER AS er morselskap for 1 datterselskap:

Frequently asked questions about ÅS KONTORSENTER AS

Who owns ÅS KONTORSENTER AS?

ÅS NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of ÅS KONTORSENTER AS?

ÅS KONTORSENTER AS had revenue of NOK 20.8m in 2024.

Where is ÅS KONTORSENTER AS based?

ÅS KONTORSENTER AS has its business address in Sem.

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.