BIZTRAC BETA
COMPANY REGISTER PROFILE
988979759 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

FRAMÅS HOLDING AS

Org. no. 988979759 Limited company (AS) Øystre Slidre Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 1.9m
Incorporated 2005
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−61k kr).

FRAMÅS HOLDING AS is registered as a limited company in Øystre Slidre, Innlandet with organisation number 988979759. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investeringsvirksomhet samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −61,000
Equity
NOK 1.9m
Est. value
NOK 20.1m

Financial health · 2025

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

Who owns FRAMÅS HOLDING AS?

FRAMÅS HOLDING AS
· NOK −61,000 profit

FRAMÅS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRAMÅS HOLDING AS own?

FRAMÅS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FRAMÅS HOLDING AS

Who owns FRAMÅS HOLDING AS?

RUNE MAGNUS FRAMÅS is the largest registered owner, with 100.0%.

Who is the general manager of FRAMÅS HOLDING AS?

Rune Magnus Framås is registered as general manager of FRAMÅS HOLDING AS.

Where is FRAMÅS HOLDING AS based?

FRAMÅS HOLDING AS has its business address in Beitostølen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.