biztrac. BETA
COMPANY REGISTER PROFILE
813037912 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Graphic design and visual communication activities

BJORVAND & CO. AS

Org. no. 813037912 Limited company (AS) Kristiansand Incorporated 2014 Active
Revenue 2025 NOK 5.9m
Operating profit NOK 208,000
Equity NOK 640,000
Incorporated 2014
Share capital NOK 300,000

BJORVAND & CO. AS is registered as a limited company in Kristiansand, Agder with organisation number 813037912. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2014. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Design og grafisk produksjon og alt som står i naturlig sammenheng med dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 208,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
▲ +2 %
Operating profit
NOK 208,000
▼ −47 %
Equity
NOK 640,000
▼ −8 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
14.0%
Good
Return on total assets
Solidity
39.7%
Good
Equity as a share of total capital

Who owns BJORVAND & CO. AS?

BJORVAND & CO. AS
NOK 5.9m rev. · NOK 208,000 profit

BJORVAND & CO. AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJORVAND & CO. AS

Who owns BJORVAND & CO. AS?

Aage Bjorvand is the largest registered owner, with 50.0%.

What is the revenue of BJORVAND & CO. AS?

BJORVAND & CO. AS had revenue of NOK 5.9m in 2025.

Who is the general manager of BJORVAND & CO. AS?

Aage Bjorvand is registered as general manager of BJORVAND & CO. AS.

Where is BJORVAND & CO. AS based?

BJORVAND & CO. AS has its business address in Kristiansand S.

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.