BIZTRAC BETA
Other real estate activities on a fee or contract basis

ANSKOT EIENDOM AS

Org. no. 992073152 Limited company (AS) Haugesund Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.1m
Equity NOK −5.3m
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5,3 mill kr).
  • Nylig endring 2026-02-12 Adresseendring registrert 2026-02-12.

ANSKOT EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 992073152. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, utvikle, forvalte og selge fast eiendom, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.1m
Equity
NOK −5.3m
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-34.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ANSKOT EIENDOM AS?

ASLE SKJÆRSTAD
ANSKOT EIENDOM AS
NOK 2.2m rev. · NOK 1.1m profit

ANSKOT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANSKOT EIENDOM AS

Who owns ANSKOT EIENDOM AS?

ASLE SKJÆRSTAD is the largest registered owner, with 100.0%.

What is the revenue of ANSKOT EIENDOM AS?

ANSKOT EIENDOM AS had revenue of NOK 2.2m in 2025.

Where is ANSKOT EIENDOM AS based?

ANSKOT EIENDOM AS has its business address in Haugesund.

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.