BIZTRAC BETA
Other health services

POLYBOS AS

Org. no. 995928825 Limited company (AS) Tønsberg Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 344,000
Equity NOK 1.4m
Incorporated 2010
Share capital NOK 100,000

POLYBOS AS is registered as a limited company in Tønsberg, Vestfold with organisation number 995928825. The business is classified under other health services (NACE 86.993). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og drive virksomhet innen fagområdet medisin, knyttet til formidling av kunnskap og tjenesteyting innen dette fagområdet samt virksomhet som står i naturlig sammenheng med dette, herunder å delta i andre selskaper med samme formål. ”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 344,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 344,000
Equity
NOK 1.4m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns POLYBOS AS?

SOFIE HEXEBERG
POLYBOS AS
NOK 2.8m rev. · NOK 344,000 profit

POLYBOS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does POLYBOS AS own?

POLYBOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about POLYBOS AS

Who owns POLYBOS AS?

SOFIE HEXEBERG is the largest registered owner, with 50.0%.

What is the revenue of POLYBOS AS?

POLYBOS AS had revenue of NOK 2.8m in 2024.

Who is the general manager of POLYBOS AS?

Erik Hexeberg is registered as general manager of POLYBOS AS.

Where is POLYBOS AS based?

POLYBOS AS has its business address in Tønsberg.

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.