BIZTRAC BETA
Other building completion and finishing

ANSKO AS

Org. no. 911981580 Limited company (AS) Horten Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 7.6m
Operating profit NOK 594,000
Equity NOK 552,000
Incorporated 2013
Employees 10
Share capital NOK 30,000

ANSKO AS is registered as a limited company in Horten, Vestfold with organisation number 911981580. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2013 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Yte tjenester innen bygg og anlegg, herunder kjøp, salg og utvikling av fast eiendom og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interesser i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.6m in revenue and NOK 594,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.6m
Operating profit
NOK 594,000
Equity
NOK 552,000
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns ANSKO AS?

RIMVYTIS PUCILAUSKAS
ANSKO AS
NOK 7.6m rev. · NOK 594,000 profit

ANSKO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANSKO AS

Who owns ANSKO AS?

RIMVYTIS PUCILAUSKAS is the largest registered owner, with 100.0%.

What is the revenue of ANSKO AS?

ANSKO AS had revenue of NOK 7.6m in 2025.

Who is the general manager of ANSKO AS?

Rimvytis Pucilauskas is registered as general manager of ANSKO AS.

Where is ANSKO AS based?

ANSKO AS has its business address in Horten.

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.