BIZTRAC BETA
Development of building projects

AASREMMEN AS

Org. no. 985958920 Limited company (AS) Hol Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −1.6m
Equity NOK 3.5m
Incorporated 2003
Share capital NOK 589,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AASREMMEN AS is registered as a limited company in Hol, Buskerud with organisation number 985958920. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2003. Registered share capital is NOK 589,000, divided into 651 shares. The company's stated purpose is: “Utvikling, kjøp, salg, utleie og drift av fast eiendom og annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −1.6m
Equity
NOK 3.5m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns AASREMMEN AS?

KIKUT EIENDOM AS
AASREMMEN AS
NOK 3.0m rev. · NOK −1.6m profit

AASREMMEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AASREMMEN AS

Who owns AASREMMEN AS?

KIKUT EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of AASREMMEN AS?

AASREMMEN AS had revenue of NOK 3.0m in 2024.

Who is the general manager of AASREMMEN AS?

Arne Pålgardhaugen is registered as general manager of AASREMMEN AS.

Where is AASREMMEN AS based?

AASREMMEN AS has its business address in Geilo.

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.