BIZTRAC BETA
Repair and maintenance of machinery

SKOGLUND SERVICE AS

Org. no. 924347619 Limited company (AS) Ringebu Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 157,000
Equity NOK 77,000
Incorporated 2019
Share capital NOK 30,000

SKOGLUND SERVICE AS is registered as a limited company in Ringebu, Innlandet with organisation number 924347619. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Service og reparasjoner på motorisert redskap, anskaffelse og salg av deler, vaktmestertjenester, leiekjøring og anleggsarbeider.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 157,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 157,000
Equity
NOK 77,000
Est. value
NOK 575,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SKOGLUND SERVICE AS?

BJØRN ØYVIND SKOGLUND
SKOGLUND SERVICE AS
NOK 1.3m rev. · NOK 157,000 profit

SKOGLUND SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKOGLUND SERVICE AS

Who owns SKOGLUND SERVICE AS?

BJØRN ØYVIND SKOGLUND is the largest registered owner, with 100.0%.

What is the revenue of SKOGLUND SERVICE AS?

SKOGLUND SERVICE AS had revenue of NOK 1.3m in 2025.

Who is the general manager of SKOGLUND SERVICE AS?

Bjørn Øyvind Skoglund is registered as general manager of SKOGLUND SERVICE AS.

Where is SKOGLUND SERVICE AS based?

SKOGLUND SERVICE AS has its business address in Fåvang.

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.