biztrac. BETA
COMPANY REGISTER PROFILE
829261472 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

BIO & FRESE SERVICE AS

Org. no. 829261472 Limited company (AS) Nord-Fron Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 66,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 30,000

BIO & FRESE SERVICE AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 829261472. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon av biovirke, flising av trevirke. Nydyrking og dypfresing av veg (stabilisering).”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 66,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
▲ +38 %
Operating profit
NOK 66,000
▲ +160 %
Equity
NOK 1.4m
▲ +5 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.33
Very good
Current assets ÷ current liabilities
Profitability
3.0%
Weak
Return on total assets
Solidity
62.4%
Very good
Equity as a share of total capital

Who owns BIO & FRESE SERVICE AS?

BIO & FRESE SERVICE AS
NOK 5.8m rev. · NOK 66,000 profit

BIO & FRESE SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIO & FRESE SERVICE AS

Who owns BIO & FRESE SERVICE AS?

Per Kristian Harildstad is the largest registered owner, with 50.0%.

What is the revenue of BIO & FRESE SERVICE AS?

BIO & FRESE SERVICE AS had revenue of NOK 5.8m in 2025.

Who is the general manager of BIO & FRESE SERVICE AS?

Marius Bondestad is registered as general manager of BIO & FRESE SERVICE AS.

Where is BIO & FRESE SERVICE AS based?

BIO & FRESE SERVICE AS has its business address in Vinstra.

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

Report a problem

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