BIZTRAC BETA
Accounting and bookkeeping

SKARVEN EIENDOM AS

Org. no. 995939096 Limited company (AS) Skjervøy Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 803,000
Operating profit NOK 219,000
Equity NOK 1.0m
Incorporated 2010
Share capital NOK 1.0m

Signals

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

SKARVEN EIENDOM AS is registered as a limited company in Skjervøy, Troms with organisation number 995939096. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2010. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom. Selskapet kan ved aksjetegning eller på annen måte delta i andre selskap”. The most recent filed accounts, for the 2025 financial year, show NOK 803,000 in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 803,000
Operating profit
NOK 219,000
Equity
NOK 1.0m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SKARVEN EIENDOM AS?

SKARVUNGEN AS
SKARVEN EIENDOM AS
NOK 803,000 rev. · NOK 219,000 profit

SKARVEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKARVEN EIENDOM AS

Who owns SKARVEN EIENDOM AS?

SKARVUNGEN AS is the largest registered owner, with 100.0%.

What is the revenue of SKARVEN EIENDOM AS?

SKARVEN EIENDOM AS had revenue of NOK 803,000 in 2025.

Who is the general manager of SKARVEN EIENDOM AS?

Vidar Brox-Antonsen is registered as general manager of SKARVEN EIENDOM AS.

Where is SKARVEN EIENDOM AS based?

SKARVEN EIENDOM AS has its business address in Skjervøy.

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.