BIZTRAC BETA
Joinery installation

FAGBYGG INNLANDET AS

Org. no. 935706033 Limited company (AS) Ringsaker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 5,000
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

FAGBYGG INNLANDET AS is registered as a limited company in Ringsaker, Innlandet with organisation number 935706033. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen snekkerarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 5,000
Equity
NOK 20,000
Est. value
NOK 27,000

Financial health · 2025

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

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

Who owns FAGBYGG INNLANDET AS?

KAY SLETTUM
FAGBYGG INNLANDET AS
NOK 2.4m rev. · NOK 5,000 profit

FAGBYGG INNLANDET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FAGBYGG INNLANDET AS

Who owns FAGBYGG INNLANDET AS?

KAY SLETTUM is the largest registered owner, with 50.0%.

What is the revenue of FAGBYGG INNLANDET AS?

FAGBYGG INNLANDET AS had revenue of NOK 2.4m in 2025.

Who is the general manager of FAGBYGG INNLANDET AS?

Kay Slettum is registered as general manager of FAGBYGG INNLANDET AS.

Where is FAGBYGG INNLANDET AS based?

FAGBYGG INNLANDET AS has its business address in Brumunddal.

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.