BIZTRAC BETA
Manufacture of outerwear

ALMANKÅS EIGEDOM AS

Org. no. 910123335 Limited company (AS) Midt-Telemark Incorporated 1968 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 876,000
Incorporated 1968
Share capital NOK 693,000

Signals

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

ALMANKÅS EIGEDOM AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 910123335. The business is classified under manufacture of outerwear (NACE 14.210). The company was incorporated in 1968. Registered share capital is NOK 693,000, divided into 315 shares. The company's stated purpose is: “Eige og forvalte fast eigedom samt delta i anna verksemd som naturlig fell inn under dette ved aksjekjøp eller på annan måte.”.

Key figures · 2024

Operating profit
NOK −23,000
Equity
NOK 876,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns ALMANKÅS EIGEDOM AS?

HUSHOLDING AS
ALMANKÅS EIGEDOM AS
· NOK −23,000 profit

ALMANKÅS EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ALMANKÅS EIGEDOM AS own?

ALMANKÅS EIGEDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ALMANKÅS EIGEDOM AS

Who owns ALMANKÅS EIGEDOM AS?

HUSHOLDING AS is the largest registered owner, with 52.4%.

Who is the general manager of ALMANKÅS EIGEDOM AS?

Tor Eilev Almankås is registered as general manager of ALMANKÅS EIGEDOM AS.

Where is ALMANKÅS EIGEDOM AS based?

ALMANKÅS EIGEDOM AS has its business address in Bø I Telemark.

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.