BIZTRAC BETA
Retail sale of clothing

ACCOUNTIT HYLLE15 AS

Org. no. 919780185 Limited company (AS) Tvedestrand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK −7,000
Incorporated 2017
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-04-01 Adresseendring registrert 2026-04-01.

ACCOUNTIT HYLLE15 AS is registered as a limited company in Tvedestrand, Agder with organisation number 919780185. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester og andre rådgivende tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK −7,000

Financial health · 2025

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

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

Who owns ACCOUNTIT HYLLE15 AS?

Iver Espegren Kappelslåen
ACCOUNTIT HYLLE15 AS
NOK 0 rev. · NOK −13,000 profit

ACCOUNTIT HYLLE15 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ACCOUNTIT HYLLE15 AS

Who owns ACCOUNTIT HYLLE15 AS?

Iver Espegren Kappelslåen is the largest registered owner, with 40.0%.

What is the revenue of ACCOUNTIT HYLLE15 AS?

ACCOUNTIT HYLLE15 AS had revenue of NOK 0 in 2025.

Where is ACCOUNTIT HYLLE15 AS based?

ACCOUNTIT HYLLE15 AS has its business address in Nes Verk.

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.