BIZTRAC BETA
Activities of tour guides

FYRST OG FREMST AS

Org. no. 825194932 Limited company (AS) Lom Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 40,000
Equity NOK 250,000
Incorporated 2020
Employees 9
Share capital NOK 30,000

FYRST OG FREMST AS is registered as a limited company in Lom, Innlandet with organisation number 825194932. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2020 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å arrangere opplevelsesturisme, bre og fjellguiding og alt som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 40,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 40,000
Equity
NOK 250,000
Est. value
NOK 327,000

Financial health · 2024

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

Who owns FYRST OG FREMST AS?

IVER LUND AAKRE
FYRST OG FREMST AS
NOK 1.3m rev. · NOK 40,000 profit

FYRST OG FREMST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FYRST OG FREMST AS own?

FYRST OG FREMST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FYRST OG FREMST AS

Who owns FYRST OG FREMST AS?

IVER LUND AAKRE is the largest registered owner, with 100.0%.

What is the revenue of FYRST OG FREMST AS?

FYRST OG FREMST AS had revenue of NOK 1.3m in 2024.

Who is the general manager of FYRST OG FREMST AS?

Iver Lund Aakre is registered as general manager of FYRST OG FREMST AS.

Where is FYRST OG FREMST AS based?

FYRST OG FREMST AS has its business address in Lom.

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.