biztrac. BETA
COMPANY REGISTER PROFILE
998467381 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

YTTERSØ BUSINESSPARK OFFICE AS

Org. no. 998467381 Limited company (AS) Larvik Incorporated 2012 Active
Revenue 2025 NOK 15.4m
Operating profit NOK 10.1m
Equity NOK 15.6m
Incorporated 2012
Share capital NOK 965,000

YTTERSØ BUSINESSPARK OFFICE AS is registered as a limited company in Larvik, Vestfold with organisation number 998467381. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 965,000, divided into 96470 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som derned står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.4m in revenue and NOK 10.1m in operating profit.

Key figures · 2025

Revenue
NOK 15.4m
▲ +5 %
Operating profit
NOK 10.1m
▲ +11 %
Equity
NOK 15.6m
▲ +32 %
Est. value
NOK 27.1m

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
12.0%
Good
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns YTTERSØ BUSINESSPARK OFFICE AS?

YTTERSØ BUSINESSPARK OFFICE AS
NOK 15.4m rev. · NOK 10.1m profit

YTTERSØ BUSINESSPARK OFFICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YTTERSØ BUSINESSPARK OFFICE AS

Who owns YTTERSØ BUSINESSPARK OFFICE AS?

YTTERSØ BUSINESSPARK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of YTTERSØ BUSINESSPARK OFFICE AS?

YTTERSØ BUSINESSPARK OFFICE AS had revenue of NOK 15.4m in 2025.

Where is YTTERSØ BUSINESSPARK OFFICE AS based?

YTTERSØ BUSINESSPARK OFFICE AS has its business address in Larvik.

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

Report a problem

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