BIZTRAC BETA
COMPANY REGISTER PROFILE
989234439 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Manufacture of bread; manufacture of fresh pastry goods and cakes

SELVIG & CO AS

Org. no. 989234439 Limited company (AS) Horten Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 795,000
Equity NOK 992,000
Incorporated 2005
Share capital NOK 300,000

SELVIG & CO AS is registered as a limited company in Horten, Vestfold with organisation number 989234439. The business is classified under manufacture of bread; manufacture of fresh pastry goods and cakes (NACE 10.710). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Eie og forvaltning av selskaper, aksjer og eiendommer samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 795,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▲ +0 %
Operating profit
NOK 795,000
▲ +1 %
Equity
NOK 992,000
▼ −25 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
49.0%
Very good
Return on total assets
Solidity
67.4%
Very good
Equity as a share of total capital

Who owns SELVIG & CO AS?

SELVIG & CO AS
NOK 1.0m rev. · NOK 795,000 profit

SELVIG & CO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SELVIG & CO AS own?

SELVIG & CO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SELVIG & CO AS

Who owns SELVIG & CO AS?

BØRRE SELVIG is the largest registered owner, with 100.0%.

What is the revenue of SELVIG & CO AS?

SELVIG & CO AS had revenue of NOK 1.0m in 2025.

Where is SELVIG & CO AS based?

SELVIG & CO AS has its business address in Horten.

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.